This report does not block or authorize the manifest or ZIP.
The audit confirms unsafe archive extraction with zipfile.extractall on Office archives and privilege-escalating sudo install guidance. Most other static hits are false positives from OOXML namespace URLs, Markdown backticks, XML examples, JavaScript template literals, and local validation code. Static review was capped at 400/508 representative findings; omitted static matches are unconfirmed, so automatic publishing stays disabled until manual review.
Report position
Historical report
Open audit history before using this report to install.
Audit attestation
Not attestable
The required immutable binding is incomplete.
Human verification
Not verified
No human verification is recorded for this report.
Coverage
56 Files scanned · 26,538 Lines analyzed
14 items shown for review
Limitations
This report does not claim runtime or sandbox execution and does not prove the absence of side effects.
01
Evidence chain
Follow the evidence from source binding to the install contract. Available evidence supports verification; it is not a safety guarantee.
zipfile.extractall is used on Office archives without validating member paths. A crafted archive could escape the target directory with zip-slip paths.
zipfile.extractall is used on Office archives without validating member paths. A crafted archive could escape the target directory with zip-slip paths.
zipfile.extractall is used on Office archives without validating member paths. A crafted archive could escape the target directory with zip-slip paths.
zipfile.extractall is used on Office archives without validating member paths. A crafted archive could escape the target directory with zip-slip paths.
This zipfile usage is part of the same archive extraction workflow that uses extractall without path validation. It should stay linked to the zip-slip risk.
This zipfile usage is part of the same archive extraction workflow that uses extractall without path validation. It should stay linked to the zip-slip risk.
This zipfile usage is part of the same archive extraction workflow that uses extractall without path validation. It should stay linked to the zip-slip risk.
with zipfile.ZipFile(self.original_file, "r") as zip_ref:
This zipfile usage is part of the same archive extraction workflow that uses extractall without path validation. It should stay linked to the zip-slip risk.
This zipfile usage is part of the same archive extraction workflow that uses extractall without path validation. It should stay linked to the zip-slip risk.
with zipfile.ZipFile(self.original_file, "r") as zip_ref:
This zipfile usage is part of the same archive extraction workflow that uses extractall without path validation. It should stay linked to the zip-slip risk.
This zipfile usage is part of the same archive extraction workflow that uses extractall without path validation. It should stay linked to the zip-slip risk.
with zipfile.ZipFile(self.original_docx, "r") as zip_ref:
This zipfile usage is part of the same archive extraction workflow that uses extractall without path validation. It should stay linked to the zip-slip risk.
03
Risk findings
Confirmed security concerns are separated from items that still need review.
No confirmed security findings were recorded for this completed audit.
04
Remediation
Suggested fixes recorded by this audit. Applying them is the maintainer’s responsibility.
FIX-001
High
Unsafe ZIP extraction of Office documents
Replace every extractall call with safe member extraction that rejects absolute paths, drive prefixes, symlinks, and paths escaping the destination directory.