JetherVerse News
Security· 1 min read

GitHub will pause Dependabot alerts on inactive repositories

From December 8, 2026, GitHub turns off Dependabot alerts on most repositories with no activity in the past year. Existing alerts are archived, not deleted. A single push restores them.

By JetherVerse News

GitHub announced on November 10, 2026 a change to Dependabot. Starting December 8, 2026, GitHub will turn off Dependabot alerts on most repositories with no activity in the past year.

GitHub counts three actions as activity. You push to any branch or tag, you create the repository, or you turn on Dependabot alerts. Alerts already open on an affected repository are archived, not deleted. Any push turns alerts back on, restores the archived alerts and restarts the one year clock. You also re-enable alerts in the repository settings.

Some repositories keep their alerts regardless of activity. These include repositories with an enforced security configuration enabling Dependabot alerts, and repositories in enterprises whose policy stops administrators from enabling or disabling alerts. The change covers all plans on github.com and GitHub Enterprise Cloud with data residency. For data residency customers, archived alerts stay in the same region as the other enterprise data. GitHub Enterprise Server is not affected.

GitHub says the change keeps Dependabot "fast and reliable" for actively developed repositories as vulnerability discovery and alert volume grow.

Quiet repositories still carry risk. Old client projects, finished prototypes and forgotten libraries sit in many accounts with known vulnerabilities in their dependencies. After December 8, you stop seeing alerts on those repositories unless you push or turn alerts back on. Audit your repository list before the date. Decide which repositories are finished and which still run in production. Archive the first group and monitor the second. Look for repositories with no push in the past year, since GitHub pauses those. A small push, such as a README edit, restarts the clock and restores the alerts.

If you maintain code for clients, a yearly review of dormant repositories belongs on your maintenance checklist.

Source: GitHub Changelog

Get the news in your inbox

The tech stories that matter from JetherVerse News, with the source on every one.

Free. Unsubscribe any time.