PDF Anonymizer HTTP service
A thin FastAPI wrapper around pdf-anonymizer-core. It does not depend on the CLI. There is no authentication.
pip install pdf-anonymizer-api
pdf-anonymizer-api --host 127.0.0.1 --port 8000
Docker files live in this package. From the repository root:
docker compose -f packages/pdf-anonymizer-api/docker-compose.yml up --build
Docs: HTTP service and Docker.
1 maintainer
Metadata
1 maintainer
Release files for pdf-anonymizer-api 0.30.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pdf_anonymizer_api-0.30.0.tar.gz | 4.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pdf_anonymizer_api-0.30.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.2 kB
Release files / pdf_anonymizer_api-0.30.0.tar.gz
| Download URL | pdf_anonymizer_api-0.30.0.tar.gz |
|---|---|
| Size | 4.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f10683f7293b0056c83e458a1087f19d011e4e60fa053bce0d8b0c3ccf1b28fe
|
|
BLAKE2b-256 checksum How to use checksums |
88724c4a0682e0d3ff559ed5690e04d0721e2bd6dc37e675e455c337d2af346f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 22, 2026.
Transparency logRelease files / pdf_anonymizer_api-0.30.0-py3-none-any.whl
| Download URL | pdf_anonymizer_api-0.30.0-py3-none-any.whl |
|---|---|
| Size | 5.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9af5806586912b79614333fe9a9949f5443f58f028e82e92333a6c2830d77ac4
|
|
BLAKE2b-256 checksum How to use checksums |
837ab2c783137379d0ceaefc3d38a387ec5311e7dadf1f744888ec88f00f3a89
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 22, 2026.
Transparency log
