Harden npm release supply chain - #3
Merged
Merged
Conversation
Zk-nd3r
marked this pull request as ready for review
August 4, 2026 18:05
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
Hardens the npm release path against the Keyv/cacheable supply-chain attack class where compromised source and CI can still produce valid npm provenance.
origin/mainValidation
npm audit signaturesnpm audit: 0 vulnerabilitiesRelease boundary
Publication remains held. This PR does not create or move a tag and does not publish npm. A future release remains blocked until npm stage-only trusted publishing, package-level disallow-token/2FA controls, and independent main/tag protections are verified. Existing
v0.2.1is unchanged.