fix: pin keyv/flat-cache/file-entry-cache to safe versions - #379
Merged
Conversation
Adds npm overrides pinning keyv 4.5.4, flat-cache 4.0.1, and file-entry-cache 8.0.0 (dev-only, via eslint) in response to the Aug 4 2026 keyv/Shai-Hulud supply chain attack. Our locked versions were already on safe majors; the overrides guarantee compromised releases (keyv 6.0.0, flat-cache 6.1.24, file-entry-cache 11.1.6) can never be resolved even via future transitive range changes. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
In response to today's (Aug 4, 2026) keyv / Shai-Hulud supply chain attack, this pins the three affected packages that appear in our dependency tree to exact known-good versions via npm
overrides:keyv→ 4.5.4flat-cache→ 4.0.1file-entry-cache→ 8.0.0Assessment
eslint, and the lockfile already pinned them to safe majors — the compromised releases (keyv 6.0.0, flat-cache 6.1.24, file-entry-cache 11.1.6) are unreachable from our semver ranges.cacheable,cacheable-request,cache-manager,ecto,@cacheable/*) are not in the tree at all.npm ci, so CI/production installs exactly the lockfile.The overrides are defense in depth: they guarantee the safe versions win even if a future (or trojanized) transitive dependency requests a newer range. Lockfile was re-synced with
npm install --package-lock-only; the only other diff is npm recording bundled-dep metadata for@tailwindcss/oxide-wasm32-wasi(no version changes).🤖 Generated with Claude Code