DocFence 0.46.0 enforces single package-specific object ID in OPC signatures
DocFence 0.46.0 introduces a stricter structural rule requiring that OPC package signatures contain exactly one object identified as idPackageObject, with a precise child topology of one ds:Manifest followed by one ds:SignatureProperties. Any nonstandard identifier, duplicate object, missing element, or extra child renders package coverage unavailable rather than partially valid. The tool performs only static declaration review and does not validate cryptographic integrity, certificates, or transform execution. Alongside this release, the Document Change Assurance Benchmark was updated to version 0.32.0 to normalize its fixture carriers to the standard idPackageObject identifier while retaining all 42 existing test cases. All 67 tests in the DocFence suite passed, and the full benchmark corpus remains publicly available on Hugging Face.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in