Repository navigation
Update from code changes: document archive extraction limits - #1157
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
📊 Automated PR Analysis
SummaryThis PR documents newly added archive extraction preflight checks and limits (ARCHIVE_MAX_ENTRIES, ARCHIVE_MAX_EXPANDED_BYTES) introduced in a related PR, updating SECRETS.md, SECURITY_ASSESSMENT.md, and THREAT_MODEL.md accordingly. It adds a risk-register entry and explains error messages and how to adjust the limits via environment variables. Review Checklist
Analyzed automatically by wshm · This is an automated analysis, not a human review. |



Summary
Documents the archive preflight checks and the two new optional limit env vars added in #1149.
Changes
SECRETS.md§1: addedARCHIVE_MAX_ENTRIES(default 50,000) andARCHIVE_MAX_EXPANDED_BYTES(default 250 GiB) rows, plus an "Archive extraction limits" subsection. It lists every refusal reason with its error message and shows how to raise the limits.SECURITY_ASSESSMENT.md: new risk-register row for untrusted archive extraction (decompression bombs, path traversal, links).THREAT_MODEL.md§6: added archive extraction to the mitigations index.Context
Source: #1149 (archive bounds portion only).