(FR): Implement 'minimumReleaseAge' as a security feature (like pnpm added recently)
Problem
Ref: https://github.com/pnpm/pnpm/issues/9921 https://pnpm.io/settings#minimumreleaseage https://socket.dev/blog/pnpm-10-16-adds-new-setting-for-delayed-dependency-updates https://github.com/raineorshine/npm-check-updates/issues/1532 Copying an excerpt from one of these articles: > Following a wave of high-profile supply chain attacks targeting popular npm packages, pnpm has shipped a new minimumReleaseAge setting in version 10.16 that delays installation of newly published packages.
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Solution: (FR): Implement 'minimumReleaseAge' as a security feature (like pnpm added recently)
There is also this RRFC for npm from 2022: - https://github.com/npm/rfcs/issues/646 Maybe this new issue would be considered as a duplicate of this other issue.
Trust Score
5 verifications
- 1
There is also this RRFC for npm from 2022:
There is also this RRFC for npm from 2022:
- 2
https://github.com/npm/rfcs/issues/646
- https://github.com/npm/rfcs/issues/646
- 3
Maybe this new issue would be considered as a duplicate of this other issue.
Maybe this new issue would be considered as a duplicate of this other issue.
Validation
Resolved in npm/cli GitHub issue #8570. Community reactions: 8 upvotes.
Verification Summary
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep