The useful question is what changes for users, developers or buyers, and whether the announcement stays industry context or becomes something people can actually use.

In September 2025, attackers phished an npm maintainer and published malicious versions of widely used packages like chalk and debug, downloaded over 2 billion times weekly. The poisoned code rewrote cryptocurrency wallet addresses in browser apps and remained live for two hours before removal. Automated update tools often pull such releases immediately, exposing projects to supply chain attacks before human review or scanning occurs. A cooldown period changes this dynamic by delaying version adoption, allowing time for detection and removal of malicious releases before they reach development pipelines.

Dependabot’s new default three-day cooldown applies only to version updates, not security patches, which remain immediate to address public vulnerabilities. The cooldown can be adjusted via the dependabot.yml configuration file, enabling teams to tailor the delay to their risk tolerance. This default aligns with practices observed in the community, where similar cooldowns are used to balance speed and scrutiny. The change targets fast-moving attacks where malicious versions are published, spread, and caught within hours, reducing the window for automated adoption.

GitHub’s Advisory Database recorded over 6,500 npm malware advisories in the year ending May 2026, up from roughly 6,200 the prior year, averaging 18 new malicious packages daily. A review of 21 supply chain incidents from 2018 to 2026 found malicious versions were typically removed within hours, suggesting a three-day cooldown would have filtered most of these releases. The default balances security needs with workflow efficiency, ensuring dependencies stay current without unnecessary delays. Teams can still customize the cooldown duration to fit their projects’ requirements.

The cooldown is one layer in a broader defense strategy against supply chain risks, complementing practices like dependency pinning, disabling install scripts in CI, and token scoping. GitHub emphasizes that this change does not address slower, more sophisticated attacks such as backdoors or maintainer sabotage. The feature is enabled by default, requiring no action to activate, and can be fine-tuned via Dependabot’s configuration options. Teams are encouraged to share feedback in community discussions to refine its performance.