pylopdf
Edit, render, extract, and create PDFs in Python.
pylopdf aims to give Python programs complete control of PDF: every feature of the PDF 2.0 specification read, interpreted, created, edited, and preserved, including everything that pymupdf does with PDF files, through a smaller API of its own. The roadmap defines the scope, exclusions, and evidence required for a completeness claim; API stability at v1.0 alone will not establish complete coverage. It is built on the Rust PDF engines lopdf, hayro, and krilla, released under the MIT license, and installs as a single wheel with no required Python dependencies.
Documentation · Getting started · API reference · Migrating from pymupdf
Status: pylopdf is pre-1.0. Version 0.16 redesigned its API, as the roadmap describes; the migration guide covers code written for pymupdf or pylopdf 0.15. Complete control is the goal, not yet the state: the roadmap's assessment lists the gaps. The stability policy explains what may change.
Install
pip install pylopdf
Python 3.11 or newer. Wheels are available for Linux, macOS, and Windows, including free-threaded Python 3.14t and 3.15t.
Optional extras add fonts and OCR models:
| Extra | Adds |
|---|---|
jp, ko, zh-cn, zh-tw |
Japanese, Korean, and Chinese fonts for displaying and writing text |
ar, he, hi, th |
Arabic, Hebrew, Hindi, and Thai fonts for writing text |
ocr |
An offline OCR engine for scanned pages |
pip install "pylopdf[jp,ocr]"
Quickstart
import pylopdf
doc = pylopdf.open("input.pdf")
page = doc.pages[0]
# Extract
text = page.text() # plain text
words = page.words() # words with their positions
hits = page.search("invoice") # rectangles of each match
tables = page.tables() # tables with their cell text
markdown = doc.markdown() # whole document as Markdown
# Render
page.pixmap(dpi=150).save("page.png")
svg = page.svg()
# Add content
with page.draw() as canvas:
canvas.text("Approved", (72, 72), size=20, fill=pylopdf.Color(0.8, 0, 0))
canvas.image((72, 100, 200, 200), "logo.png")
page.annotations.add(pylopdf.Highlight(hits))
# Reorganize pages (fetch pages again with doc.pages[i] afterwards)
del doc.pages[1:3]
doc.pages.extend(pylopdf.open("appendix.pdf").pages) # append another document
# Save, compressed and without unused objects
doc.save("output.pdf")
The getting started guide covers each area in more detail.
Features
- Pages and documents: merge, split, reorder, rotate, and delete pages; table of contents, page labels, metadata, and file attachments
- Text extraction: plain or positioned text, search, tables, Markdown output, and vertical Japanese/Chinese text
- Rendering: pages to PNG or SVG, with parallel rendering of many pages
- Adding content: text in any font with proper shaping, images, vector drawings, pages from other PDFs, highlights, and links
- Forms: fill in form fields
- OCR: make scanned pages searchable without installing Tesseract
- Saving: compression, cleanup of unused objects, incremental updates that keep signatures valid, and AES-256 or AES-128 encryption
Why pylopdf
- MIT licensed. pymupdf is AGPL or commercial.
- Small and self-contained. About 7 MB per wheel, with nothing else to install, so it fits AWS Lambda and similar environments. It also runs in WebAssembly, including Cloudflare Python Workers.
- Safe with untrusted files. Size and complexity limits raise a clear
LimitErrorinstead of exhausting memory;DocumentLimits.web()enables all of them. See the security model. - Built for concurrency. Heavy operations release the GIL, and free-threaded Python is supported. See the concurrency guide.
Not supported yet
Redaction, editing or deleting annotations, creating form fields, and validated PDF/A and PDF/UA output are planned; the roadmap lists them.
Typesetting with HTML and CSS and digital signatures stay with ecosystem tools. The ecosystem guide shows how to pair pylopdf with typst and pyHanko for those.
Benchmarks
Benchmarks against pymupdf are reproducible from this repository, and the results include the cases where pylopdf is slower. See the benchmark page.
Contributing
Bug reports and pull requests are welcome. Building from source needs a Rust toolchain and uv:
uv sync
uv run pytest
CONTRIBUTING.md has the full development guide. Please report security issues privately through GitHub Security Advisories.
License
MIT. pylopdf is built on lopdf, hayro, krilla, and HarfRust; see NOTICE.md for third-party licenses.
Metadata
Release files for pylopdf 0.16.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 | Provenance | Actions |
|---|---|---|---|---|
| pylopdf-0.16.0.tar.gz | 862.6 kB | With provenance | Details for pylopdf-0.16.0.tar.gz |
Built distributions (wheels)
Total release size: 156.9 MB
Release files / pylopdf-0.16.0.tar.gz
| Download URL | pylopdf-0.16.0.tar.gz |
|---|---|
| Size | 862.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f8facb2e3f182ab930badc10f1540a5c0b7af141c811a43cac679b695aba8c95
|
|
BLAKE2b-256 checksum How to use checksums |
c898a39e3d7b91253c740c3532ba94c7fb6de895fde859659e3179a68cc2e2c2
|
| 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 Oct 27, 2026.
Transparency logRelease files / pylopdf-0.16.0-cp315-cp315t-win_amd64.whl
| Download URL | pylopdf-0.16.0-cp315-cp315t-win_amd64.whl |
|---|---|
| Size | 10.3 MB |
| Tags | CPython 3.15 CPython 3.15 free-threading Windows x86-64 |
|
SHA-256 checksum How to use checksums |
5f491ff565e8805685115cfcd4bdd73c8294b1787de0ef5f7a8e1322528e1bea
|
|
BLAKE2b-256 checksum How to use checksums |
2c2cfb690a6111fcb13d6b947b892182966f7ed37bbad0123d887ab780cd5e44
|
| 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 Oct 27, 2026.
Transparency logRelease files / pylopdf-0.16.0-cp315-cp315t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pylopdf-0.16.0-cp315-cp315t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 10.6 MB |
| Tags | CPython 3.15 CPython 3.15 free-threading Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
d2299866e0b087f90f8dff764ba3cabc748ca0aa4a7d6ddc3871e2bb50b9a727
|
|
BLAKE2b-256 checksum How to use checksums |
783e8bc91b17e07b7368131fa4265985a1e8b5c9f5acb0a6c0df0d813512f595
|
| 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 Oct 27, 2026.
Transparency logRelease files / pylopdf-0.16.0-cp315-cp315t-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | pylopdf-0.16.0-cp315-cp315t-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 9.8 MB |
| Tags | CPython 3.15 CPython 3.15 free-threading Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
c233a76a3c8427e3ab697467bfdf0e38508ca3df46e5a6197cb9c17c3b71e649
|
|
BLAKE2b-256 checksum How to use checksums |
caa9b8a0b356b85798974bed8641878b6387b67d8787ed5118fed746dfbd9a62
|
| 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 Oct 27, 2026.
Transparency logRelease files / pylopdf-0.16.0-cp315-cp315t-macosx_11_0_arm64.whl
| Download URL | pylopdf-0.16.0-cp315-cp315t-macosx_11_0_arm64.whl |
|---|---|
| Size | 9.2 MB |
| Tags | CPython 3.15 CPython 3.15 free-threading macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
26380772756843b1e55d6881d8d81925d42afeb5b7cf2d4ae7efa15c049fb8b5
|
|
BLAKE2b-256 checksum How to use checksums |
9194306cb4228d383db24842dccfc7b48d7143be9413aefecd44ebbe51a963fd
|
| 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 Oct 27, 2026.
Transparency logRelease files / pylopdf-0.16.0-cp315-cp315t-macosx_10_12_x86_64.whl
| Download URL | pylopdf-0.16.0-cp315-cp315t-macosx_10_12_x86_64.whl |
|---|---|
| Size | 10.2 MB |
| Tags | CPython 3.15 CPython 3.15 free-threading macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
f2e9d3f372ecbacb0f298feb3c8e4b7a5863189812ad21148e7db3f1b1846ba2
|
|
BLAKE2b-256 checksum How to use checksums |
19964af51727cdca75e4eb2b344692a9edc09c955a16c3a86b0dec9265ef8451
|
| 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 Oct 27, 2026.
Transparency logRelease files / pylopdf-0.16.0-cp314-cp314t-win_amd64.whl
| Download URL | pylopdf-0.16.0-cp314-cp314t-win_amd64.whl |
|---|---|
| Size | 10.3 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Windows x86-64 |
|
SHA-256 checksum How to use checksums |
267eb40a1d2bbbaf1129cb3885263c81d390faaae1164f04270d9d632be1a2d2
|
|
BLAKE2b-256 checksum How to use checksums |
6658c31a522881c8585c25074df50b0f4ef2b0986d24cd7a52c4b20c2fa28967
|
| 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 Oct 27, 2026.
Transparency logRelease files / pylopdf-0.16.0-cp314-cp314t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pylopdf-0.16.0-cp314-cp314t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 10.6 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
dcb559f8cd77da68a86dd69ae22d2b60d0786eb91113ff4a4c73c60593afb791
|
|
BLAKE2b-256 checksum How to use checksums |
ce9da8d3fa530675663e0aa2601bd939153585b7673c5e9269a44176c1e4e17f
|
| 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 Oct 27, 2026.
Transparency logRelease files / pylopdf-0.16.0-cp314-cp314t-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | pylopdf-0.16.0-cp314-cp314t-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 9.8 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
2f9a2c17d64c10eccff8a40ea5c2b79a987f0cca82df541ef235fa5f257a0df1
|
|
BLAKE2b-256 checksum How to use checksums |
b2f565c93c11f1b0153df880c243d9da93850ebc1f66698cc3a54ef064917421
|
| 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 Oct 27, 2026.
Transparency logRelease files / pylopdf-0.16.0-cp314-cp314t-macosx_11_0_arm64.whl
| Download URL | pylopdf-0.16.0-cp314-cp314t-macosx_11_0_arm64.whl |
|---|---|
| Size | 9.2 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
9500b0c0aac17a12868b3bf4064b2fee20648eda76543fd835cb5c921e4c5e60
|
|
BLAKE2b-256 checksum How to use checksums |
5f47fb6df13cc6fc099877a8d4e6a8c1a021b51dc94d26ccf5703de2f60c8783
|
| 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 Oct 27, 2026.
Transparency logRelease files / pylopdf-0.16.0-cp314-cp314t-macosx_10_12_x86_64.whl
| Download URL | pylopdf-0.16.0-cp314-cp314t-macosx_10_12_x86_64.whl |
|---|---|
| Size | 10.2 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
b45f8ee03cdd500116614df4a698db261f3a176b8e054e9b56bc3bab42c170ab
|
|
BLAKE2b-256 checksum How to use checksums |
791bff06edff83adde9c41ee09314dced7fc8e61487409c517b71fc77afc53e0
|
| 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 Oct 27, 2026.
Transparency logRelease files / pylopdf-0.16.0-cp311-abi3-win_amd64.whl
| Download URL | pylopdf-0.16.0-cp311-abi3-win_amd64.whl |
|---|---|
| Size | 10.3 MB |
| Tags | CPython 3.11 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
1e64ec537a8d419098439219c7022c5b3566f4b361253d01da8f608328c700cd
|
|
BLAKE2b-256 checksum How to use checksums |
c560ee1f02c688ad7d32e15f31b55a73a8038e4441bc8c19cb6deeb2b93754fc
|
| 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 Oct 27, 2026.
Transparency logRelease files / pylopdf-0.16.0-cp311-abi3-pyemscripten_2025_0_wasm32.whl
| Download URL | pylopdf-0.16.0-cp311-abi3-pyemscripten_2025_0_wasm32.whl |
|---|---|
| Size | 5.8 MB |
| Tags | CPython 3.11 PyEmscripten 2025.0+ WebAssembly abi3 |
|
SHA-256 checksum How to use checksums |
44a2fc89b2520e5ed05b05e27e869cf6e0468ca9ae74989e2e697a4e5ce98e4b
|
|
BLAKE2b-256 checksum How to use checksums |
7a841adead3e8b0600323fdc5481080527280d572af53643533161db448659c2
|
| 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 Oct 27, 2026.
Transparency logRelease files / pylopdf-0.16.0-cp311-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pylopdf-0.16.0-cp311-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 10.6 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
f944407d336abdfdc0772a763a9daadce8e6da54946860a1ecb521244f385b85
|
|
BLAKE2b-256 checksum How to use checksums |
1e47620c08846fd59e8ebeddb68b8b9f9f3ccc2d4489e6943dbec9edd20b684c
|
| 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 Oct 27, 2026.
Transparency logRelease files / pylopdf-0.16.0-cp311-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | pylopdf-0.16.0-cp311-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 9.8 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
f489fc1f0ebb38a754b8fe61e26d62dc2fe99f6479cacd209d90c6e0f8f1c70d
|
|
BLAKE2b-256 checksum How to use checksums |
fc43b823fb2d69485d6517d9a5f98c1982adca5cfddfc062683fe5987cdaf89e
|
| 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 Oct 27, 2026.
Transparency logRelease files / pylopdf-0.16.0-cp311-abi3-macosx_11_0_arm64.whl
| Download URL | pylopdf-0.16.0-cp311-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 9.3 MB |
| Tags | CPython 3.11 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
55abb5165e50dff30d6c2d3458b93a174a4d2ab32bef47798d1c01e5e8ea1843
|
|
BLAKE2b-256 checksum How to use checksums |
a80777676c9b6f2cf29c0ba05e3968c22ff4f2f5f18bb363b042a4f6d7301e9e
|
| 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 Oct 27, 2026.
Transparency logRelease files / pylopdf-0.16.0-cp311-abi3-macosx_10_12_x86_64.whl
| Download URL | pylopdf-0.16.0-cp311-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 10.1 MB |
| Tags | CPython 3.11 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
0f0741e8b6b68e6c1b60921c34146f2071024cb00764c242243e40a09e253804
|
|
BLAKE2b-256 checksum How to use checksums |
1e13124b8d7cab7cf6e0504084d6e1f9151ea09ccd2be8e5864b11744accaac6
|
| 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 Oct 27, 2026.
Transparency logSecurity for pylopdf 0.16.0
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.
Full provenance
All 17 files in this release have been uploaded with provenance metadata.
Attestation for pylopdf-0.16.0.tar.gz
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 Oct 27, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.