Wait a bit before installing new package versions #8197
Merged
Conversation
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
There has been a series of attacks on npm packages recently: https://decipher.sc/2025/09/08/targeted-attack-compromises-popular-npm-packages/ https://www.aikido.dev/blog/s1ngularity-nx-attackers-strike-again This leads to compromising the machines of devs, and from there automatically infects npm packages to which the dev (or CI pipeline) has publishing access, or GitHub push access. This commit is a band-aid quick fix, so we don't install the bleeding edge new package the minute it comes out. So far, package maintainers and NPM have been relatively quick to find and yank the infected packages. This is not guaranteed to protect us, but it should make it harder for us to automatically get infected. For reference, the renovate docs on this option: https://docs.renovatebot.com/configuration-options/#minimumreleaseage
BacLuc
reviewed
Sep 17, 2025
| }, | ||
| "automergeType": "branch", | ||
| "rebaseWhen": "conflicted", | ||
| "minimumReleaseAge": "7 days", |
There was a problem hiding this comment.
just as info: this is for everything, not just npm
There was a problem hiding this comment.
Yes, thanks for bringing it up. This is more or less on purpose. Even though the recent breaches have been on npm, other package managers and registries are not immune to such attacks.
BacLuc
approved these changes
Sep 17, 2025
simfeld
approved these changes
Sep 17, 2025
This was referenced Oct 3, 2025
Merged
Closed
Merged
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.
There has been a series of attacks on npm packages recently:
https://decipher.sc/2025/09/08/targeted-attack-compromises-popular-npm-packages/
https://www.aikido.dev/blog/s1ngularity-nx-attackers-strike-again
This leads to compromising the machines of devs, and from there automatically infects npm packages to which the dev (or CI pipeline) has publishing access, or GitHub push access. This commit is a band-aid quick fix, so we don't install the bleeding edge new package the minute it comes out. So far, package maintainers and NPM have been relatively quick to find and yank the infected packages. This is not guaranteed to protect us, but it should make it harder for us to automatically get infected.
For reference, the renovate docs on this option:
https://docs.renovatebot.com/configuration-options/#minimumreleaseage