mirror of
https://github.com/oven-sh/bun
synced 2026-02-19 07:12:24 +00:00
Previously, if a lockfile contained an integrity hash with an unrecognized algorithm (e.g., "md5-AAAA"), the tag would parse as unknown and the integrity verification would be silently skipped. This meant a tampered lockfile could disable integrity checking entirely. Now all lockfile parsers (bun.lock, yarn.lock, pnpm-lock.yaml, package-lock.json) reject non-empty integrity strings with unsupported hash algorithms. As defense-in-depth, the tarball extraction step also errors when an npm package lacks a supported integrity hash. Co-Authored-By: Claude <noreply@anthropic.com>