This repository was archived by the owner on Mar 3, 2026. It is now read-only.
Open
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Why?
Dependency cooldowns delay automatic updates for a configurable period after a new version is published. This mitigates supply chain attacks by giving the security community time to identify and report malicious packages before they're adopted.
Empirical data shows that the vast majority of supply chain attacks have a window of opportunity of less than 7 days — a 7-day cooldown would have prevented ~80% of recent high-profile attacks (xz-utils, tj-actions, Ultralytics, etc.).
Read more: https://blog.yossarian.net/2025/11/21/We-should-all-be-using-dependency-cooldowns
Changes
cooldown: default-days: 7to everypackage-ecosystementry in.github/dependabot.yml