Add npm min-release-age=7d cooldown to .npmrc#433
Merged
Conversation
Delays installation of newly-published packages by 7 days as a defense against rapid-publish supply-chain attacks. Requires npm >=11.10 to take effect; older npm silently ignores the key, so safe to commit as progressive enhancement.
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
Adds
min-release-age=7dto.npmrc— npm refuses to install package versions younger than 7 days.Why
Defense against rapid-publish supply-chain attacks:
By the time a malicious package has been live for a week, it has typically been flagged and yanked. This shifts the install-time risk window from "minutes after publish" to "after a week of public scrutiny."
How it works
npm install, lockfile updates, and CI installs alike.Test plan
npm installruns normally with no behavior change for established packages.