-
-
Notifications
You must be signed in to change notification settings - Fork 18
chore: add minimal age to package installations #270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
44c043c
to
411a03b
Compare
98c532a
to
0dd7ca3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
0dd7ca3
to
e1f68b9
Compare
e1f68b9
to
f9f77a2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea, LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Summary
This pull request enforces a 3-day minimum release age for all NPM packages. Packages published more recently will be blocked from installation, reducing the risk of supply-chain attacks involving newly compromised releases.
Teams that need exceptions can override this restriction by listing packages under the
npmPreapprovedPackages
option.This is a new feature included in yarn v4.10.*
Note
Enforces a 3-day npm package age gate in Yarn with allowlisted scopes and upgrades the project to Yarn 4.10.3.
npmMinimalAgeGate: 4320
to enforce a 3-day minimum package age in.yarnrc.yml
.npmPreapprovedPackages
allowlist for@metamask/*
and@lavamoat/*
.packageManager
to[email protected]
inpackage.json
.Written by Cursor Bugbot for commit 0dc3c9b. This will update automatically on new commits. Configure here.