Skip to content
GitHub to Pause Dependabot Alerts on Inactive Repositories

GitHub to Pause Dependabot Alerts on Inactive Repositories

First seen 10 Nov 2026, 17:48 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 10, 2026 at 17:49 UTC
  • •Dependabot alerts will pause for inactive repositories from December 8, 2026.
  • •Repositories with any activity will automatically restore alerts.
  • •Archived alerts can be restored at any time by repository administrators.

Starting December 8, 2026, GitHub will pause Dependabot alerts for repositories inactive for over a year. This change aims to enhance performance by reducing alert volume as vulnerability discovery increases. Repositories that have any activity, such as pushes or enabling alerts, will have their alerts restored. Alerts will remain active for repositories with enforced security configurations or specific enterprise policies. Archived alerts can be restored at any time. This policy applies to all GitHub plans and GitHub Enterprise Cloud, but not to GitHub Enterprise Server.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2026-11-10
Dependabot alert policy announced
GitHub announced changes to Dependabot alerts, pausing them for inactive repositories starting December 8, 2026.
Github.Blog

More articles in this cluster (2)

Common questions

What happens to archived alerts?
Archived alerts can be restored at any time by repository administrators.
How is repository activity defined?
Activity includes pushing to any branch or tag, creating the repository, or enabling Dependabot alerts.
Will alerts remain active for all repositories?
No, alerts will only remain active for repositories with enforced security configurations or specific enterprise policies.