Only the latest 0.x release receives security fixes.

An archive can lie about its paths, sizes, compression ratio, links, headers, and checksums. Bytefold validates these properties and provides bounded readers, but it is not a sandbox and cannot choose application-specific limits.

For uploaded or remote input:

• use safetyProfile: "untrusted";
• set explicit input, entry, total-output, and compression-ratio limits;
• reject failed audits before opening entry streams;
• use runtime extraction helpers instead of joining archive paths manually;
• close readers in finally;
• treat ZIP passwords as interoperability, not strong confidentiality.

See the audit guide, resource limits, and the behavior contract for details.

Use a private GitHub security advisory. Include the affected version, a minimal reproducer, and the impact. Do not put unpatched vulnerability details in a public issue.