Add min-release-age to prevent supply chain attacks - #2937
Open
judeallred wants to merge 1 commit into
Open
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
judeallred
marked this pull request as draft
May 21, 2026 18:02
Member
|
@BugBot review |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 2788a28. Configure here.
judeallred
marked this pull request as ready for review
May 21, 2026 20:01
Contributor
|
'This PR has been flagged as stale due to no activity for over 60 |
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.
See https://chia-network.atlassian.net/browse/SEC-1019 and #security_chat for context
Summary
min-release-age=1to.npmrc, telling npm to only resolve package versions published more than 1 day agoTest plan
npm installstill works correctlynpm cistill works correctlyMade with Cursor
Note
Low Risk
Low risk configuration change that only affects npm dependency resolution by avoiding newly published versions; potential impact is install failures if a required package is <1 day old.
Overview
Adds
min-release-age=1to.npmrcso npm will only resolve dependency versions published at least one day ago, reducing exposure to freshly published malicious packages.Reviewed by Cursor Bugbot for commit 2788a28. Bugbot is set up for automated code reviews on this repo. Configure here.