chore: temporarily pin Keyv and cache dependencies - #189
Merged
Conversation
Pin known-clean Keyv and cache dependency versions while the npm supply-chain incident is reviewed. Reassess and remove by the end of August 2026.\n\nRefs #188
TheRealAgentK
requested review from
ProRedCat,
QuantumNightmare and
sumitramanga
August 5, 2026 02:15
ProRedCat
approved these changes
Aug 5, 2026
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
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
Temporarily override the development-only cache dependency chain to the already-resolved known-clean versions:
keyv@4.5.4flat-cache@4.0.1file-entry-cache@8.0.0This is defense in depth during the active Keyv/Cacheable npm supply-chain incident. The known compromised releases are in newer major-version lines and no compromised package was found in the repository, lockfile, or installed tree.
The overrides apply to installs rooted in this repository; they do not impose resolutions on consumers of the published
@raygun.io/aws-lambdapackage.Temporary control
This must be reviewed by 31 August 2026. The removal criteria, current GitHub target date, rescanning checklist, and unroll procedure are tracked in #188.
Dependency impact
npm install --package-lock-only --ignore-scriptsproduced nopackage-lock.jsonchange because the pinned versions were already resolved.npm lsconfirms all three overrides are active.Verification
npm cinpm testnpm run eslintnpm run tseslintnpm run prettier:checknpm ls keyv flat-cache file-entry-cache --allRefs #188