GitHub Dependabot Alerts Will Pause on Inactive Repositories: What to Do Before December

GitHub will pause Dependabot alerts on most repositories with no activity for a year. Here is what changes, what counts as activity, and how to keep coverage.

A dependency graph connected to a paused security bell, calendar, and active repository path

GitHub is changing how it handles Dependabot alerts for repositories that have gone quiet. Starting December 8, 2026, GitHub will turn off Dependabot alerts on most repositories with no activity in the previous year. Existing alerts are archived, not deleted, and can be restored.

This is easy to miss if you keep old libraries, examples, archived products, or low-traffic internal tools in GitHub. A repository can look healthy in the security tab today and silently stop receiving new Dependabot alerts next month if no qualifying activity occurs.

What changes on December 8

GitHub will disable Dependabot alerts for most repositories with no activity during the past year. The existing alerts are archived rather than removed. That means the repository history is not erased, but the repository will not keep receiving the same alert coverage while alerts are off.

What counts as activity

GitHub lists three events that reset the clock: pushing to any branch or tag, creating the repository, and turning on Dependabot alerts. A push to a non-default branch counts, so a maintenance branch or scheduled dependency update can keep a repository active. Opening an issue or pull request is not listed as a qualifying event.

How to keep alerts on

The safest first step is to inventory repositories that still matter but have not changed in a year. For each one, decide whether it needs ongoing vulnerability coverage. If it does, make a real maintenance change and push it, or enable Dependabot alerts again in the repository settings. Either action restores archived alerts and starts a new one-year clock.

The enterprise exceptions

GitHub says it will not turn off alerts for repositories covered by an enforced security configuration that enables Dependabot alerts. It also skips repositories in enterprises whose Dependabot alerts policy does not allow repository administrators to enable or disable alerts. Use those controls when an organization needs consistent coverage regardless of repository activity.

What this does not mean

This is not repository archival, and it is not a deletion of the alert history. It is also not a reason to create meaningless commits. If a project is truly retired, document that decision and accept that it will not receive ongoing dependency analysis. If it is still a supported product, give it an owner and a maintenance path instead of relying on a dormant repository to protect itself.

A short preparation checklist

List repositories with production code, shipped packages, deployed infrastructure, or dependencies used by other projects. Check the last push date and whether Dependabot alerts are enabled. Mark repositories that need continuous coverage, then either assign an owner for a maintenance push or enforce the setting at the enterprise level. Finally, record how you will notice if alerts are disabled later.

Bottom line

Before December 8, separate forgotten repositories from intentionally quiet ones. Restore alerts for projects that still matter, and use enterprise policy when coverage must not depend on commit frequency. The archived alerts can come back, but the safest time to decide who owns dependency risk is before scanning pauses.