Add supply-chain cooldown for npm dependencies#80
Open
everdimension wants to merge 1 commit into
Open
Conversation
Enforce a rolling release-age cooldown so npm only resolves dependency versions that have been published for at least 15 days, reducing exposure to compromised "fresh" releases. Malicious packages are typically detected and unpublished within that window. - .npmrc: set min-release-age=15 (requires npm >= 11.10.0); - package.json: add devEngines pinning node >=20.10 and npm >=11.10; hard-fail for earlier npm versions - workflows: bump CI to Node 24 (Node 22 ships npm 10, which lacks min-release-age) and switch the publish job's npm install -> npm ci for deterministic, lockfile-pinned installs - README: document the policy and the --min-release-age=0 override for urgent security fixes No breaking changes for consumers of the published zerion-cli package: the runtime requirement stays node >=20 (engines is unchanged), and devEngines / .npmrc are dev-and-CI only. The cooldown affects only version resolution (updating package-lock.json); installs from the existing lockfile, including npm ci, are unaffected.
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.
Enforce a rolling release-age cooldown so npm only resolves dependency versions that have been published for at least 15 days, reducing exposure to compromised "fresh" releases. Malicious packages are typically detected and unpublished within that window.
No breaking changes for consumers of the published zerion-cli package: the runtime requirement stays node >=20 (engines is unchanged), and devEngines / .npmrc are dev-and-CI only. The cooldown affects only version resolution (updating package-lock.json); installs from the existing lockfile, including npm ci, are unaffected.