chore(security): add min-release-age=3 to .npmrc#152
Open
ms-bot wants to merge 1 commit into
Open
Conversation
ms-bot
force-pushed
the
mobsuccessbot/npmrc-min-release-age
branch
from
1b600a8 to
34986c1
Compare
There was a problem hiding this comment.
Pull request overview
Adds an npm configuration setting intended to reduce supply-chain risk by preventing installation of very recently published packages.
Changes:
- Introduces
min-release-age=3in.npmrcto require packages be at least 3 days old before install.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| @@ -0,0 +1 @@ | |||
| min-release-age=3 | |||
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
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.
Why is this needed?
This pull request has been created by a robot to add supply chain protection.
Adding
min-release-age=3to.npmrcprevents npm from installing packages published less than 3 days ago, protecting against attacks like the TanStack compromise (May 2026).