Dev News Daily ENDE

Dependabot alerts will switch off on repositories idle for a year from 8 December

GitHub announced on 10 November that, starting 8 December 2026, it will turn off Dependabot alerts on most repositories that have had no activity in the past year. The reason given is scale: with vulnerability discoveries and alert volume growing quickly, GitHub wants Dependabot to stay fast for repositories that are actively developed.

The definition of activity is short. A push to any branch or tag counts, as do creating the repository and turning Dependabot alerts on.

What happens to existing alerts matters for anyone who audits them. They are archived, not deleted, and can be restored at any time. Any push to the repository switches alerts back on automatically, and an owner can also re-enable them in the repository settings. In both cases GitHub restores the archived alerts and the one-year clock starts again.

There are two exemptions. GitHub will not turn off alerts on repositories covered by an enforced security configuration that enables Dependabot alerts, and it skips repositories in enterprises whose policy does not let repository administrators enable or disable alerts themselves. The change applies to all plans on github.com and to GitHub Enterprise Cloud with data residency, where archived alerts are stored in the enterprise's region. GitHub Enterprise Server is not affected.

Dependabot alerts will switch off on repositories idle for a year from 8 December
Dependabot alerts will switch off on repositories idle for a year from 8 December — Dev News Daily

Why it matters

A repository that nobody pushes to can still be the one other projects install, and after 8 December its owner will no longer hear about new vulnerabilities in its dependencies unless something keeps alerts on. Organisations that rely on alerts for dormant but published code can avoid the gap with an enforced security configuration, which is the exemption GitHub names.