-
Notifications
You must be signed in to change notification settings - Fork 0
Add npm min-release-age security setting #243
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -15,6 +15,7 @@ composer.lock | |
| node_modules/ | ||
| package.json | ||
| package-lock.json | ||
| .npmrc | ||
|
|
||
| # WordPress | ||
| .wordpress-org | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| min-release-age=7 | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Checked Useful? React with 👍 / 👎. |
||
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.
npm's
min-release-agedocumentation defines this value in seconds, so7delays eligible releases by only seven seconds rather than the seven days stated in the commit. This leaves the intended supply-chain protection effectively absent; use604800for seven days.Useful? React with 👍 / 👎.