chore(security): raise pnpm minimumReleaseAge to 48h - #14429
Closed
h0lybyte wants to merge 1 commit into
Closed
Conversation
…rantine) Widen the freshly-published-version quarantine window against npm supply-chain attacks (compromised releases are typically yanked within 24h). Refs #14423.
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.
Part of #14423.
Raises pnpm
minimumReleaseAgefrom720to2880(unit = minutes, so 12h → 48h).Widens the quarantine window before a freshly-published npm version is installable. Most supply-chain compromises are detected and yanked within 24h; a 48h floor means the resolver falls back to the prior known-good version during that window.
Isolated from the bwrap wrapper (#14423 item 2) — that ships separately.
Risk
Low. Only affects resolution of brand-new releases (<48h old).
--frozen-lockfileinstalls are unaffected (pinned versions already resolved in the lockfile).