NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI, #1757 most downloaded on PyPI
Validates X.509 certificates and paths; forked from wbond/certvalidator
Latest stable
0.33.0
Last release 1 months ago
17 Oct 2026
Release timing varies
gaps range from 9 days to 5 months
Nearly every release is documented
notes for 57 of 57 stable releases
4 versions withdrawn
withdrawn after publishing
6 years old
61 releases · first in 2020
The release has been uploaded to PyPI. Documentation is available on ReadTheDocs.
The release has been uploaded to PyPI. Documentation is available on ReadTheDocs.
Note: The public API is not completely stable yet, so future releases may still include API changes. This is particularly likely for the validation code and the pdf_utils package; please refer to the documentation for further details.
The release notes for the 0.12.0 release are available here.
Release date: 2022-01-26
This is largely a maintenance release, and contains no new high-level features or public API changes. As such, upgrading is strongly recommended.
The most significant change is the (rather minimalistic) support for hybrid reference files. Since working with hybrid reference files means dealing with potential ambiguity (which is dangerous when dealing with signatures), creation and validation of signatures in hybrid reference documents is only enabled in nonstrict mode. Hybrid reference files are relatively rare these days, but the internals need to be able to cope with them either way, in order to be able to update such files safely.
Significant refactor of cross-reference parsing internals. This doesn’t affect any public API entrypoints, but read the reference documentation for pyhanko.pdf_utils.xref if you happen to have code that directly relies on that internal logic.
Minimal support for hybrid reference files.
Add strict flag to IncrementalPdfFileWriter .
Expose --no-strict-syntax CLI flag in the addsig subcommand.
Ensure that signature appearance bounding boxes are rounded to a reasonable precision. Failure to do so caused issues with some viewers.
To be consistent with the purpose of the strictness flag, non-essential xref consistency checking is now only enabled when running in strict mode (which is the default).
The hybrid reference support indirectly fixes some potential silent file corruption issues that could arise when working on particularly ill-behaved hybrid reference files.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
One column per quarter.