Skip to content

PDFFence 1.18.0

Choose a tag to compare

@SybilGambleyyu SybilGambleyyu released this 07 Aug 06:58

Current semantic signature coverage requirement

  • Adds opt-in require_current_file_signature_coverage (PFP010).
  • Fails when an inspected PDF has semantic signature roots but none of their /ByteRange values reaches the current physical file end.
  • Leaves unsigned PDFs passing, and complements PFP009: it can report an already-stale boundary even when no new coverage regression occurred.

PFP010 is static review evidence only. It does not validate a signature, /Contents, digest, certificate, transform, permission, or trust decision, and it does not determine whether a later revision is safe, authorized, or malicious.

Verification

235 tests and Ruff passed; PDFCAB 1.18 scored 155/155 pairs. Two fixed-timestamp builds produced identical wheel and source archives; clean Python 3.12/3.13 wheel installs and a Python 3.12 source-archive install passed pip check, fixture verification, and the full score.