Adopt 7 day cooldown before upgrading dependencies #1956
+2
−0
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
In an effort to reduce the risk of a supply chain attack, add a 7 day cooldown between when a new version of a dependency is released and when Dependabot creates a PR upgrating to it. Most malicious packages are detected by package vendors (in our case, NPM) relatively quickly. The damage is done in the window between when a malicious package is released, and when it is identified and taken down. By adding a cooldown we narrow the window where a malicious package can be introduced, and hopefully within 7 days this window shrinks to zero and we have no potential exposure at all. At minimum this cooldown shrinks the window we're vulnerable. For a more detailed explanation of how this helps, see: https://blog.yossarian.net/2025/11/21/We-should-all-be-using-dependency-cooldowns
plemarquand
requested review from
0xTim,
adam-fowler and
award999
as code owners
award999
approved these changes
Nov 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
In an effort to reduce the risk of a supply chain attack, add a 7-day cooldown between when a new version of a dependency is released and when Dependabot creates a PR upgrading to it.
Most malicious packages are detected by package vendors (in our case, npm) relatively quickly. The damage is done in the window between when a malicious package is released and when it is identified and taken down.
By adding a cooldown, we narrow the window where a malicious package can be introduced. Ideally, within 7 days this window shrinks to zero and we have no potential exposure at all. At minimum, this cooldown reduces the window where we're vulnerable.
For a more detailed explanation of how this helps, see: https://blog.yossarian.net/2025/11/21/We-should-all-be-using-dependency-cooldowns
Tasks
Required tests have been writtenDocumentation has been updatedAdded an entry to CHANGELOG.md if applicable