GitHub Will Pause Dependabot Alerts on Dormant Repositories
From December 8, 2026, most GitHub.com repositories inactive for a year will have Dependabot alerts paused. Existing alerts are archived and can return.
On this page
A repository can stop changing while its software remains deployed. That gap is why GitHub’s November 10 announcement deserves a calendar reminder: beginning December 8, 2026, Dependabot alerts will pause on most repositories with no activity in the preceding year. A push to any branch or tag counts; creating the repository and turning alerts on also count. GitHub says archived alerts are retained and can be restored. [1]

What changes on December 8
Dependabot alerts notify repository owners when GitHub identifies a vulnerable dependency. GitHub’s documentation says detection uses the repository’s dependency graph and the GitHub Advisory Database; alerts identify the affected file, severity and, when available, a fixed version. That is one stage of supply-chain defense, alongside updating dependencies and checking whether vulnerable code is reachable in the application. [2]
Under the announced change, most repositories with no qualifying activity in the previous 12 months will have alerts turned off. This is not a deletion of the repository, its dependency graph, or its alert history. GitHub says the existing alerts will be archived. Any push automatically turns alerts back on and restores those alerts; an administrator can also enable them in repository settings. [1]
GitHub counts pushes to any branch or tag, repository creation, and enabling alerts as activity. That means the rule is based on repository events, not on whether the default branch changed, whether a deployment is active, or whether someone still imports the package. A project can be operationally important while appearing quiet to this mechanism. [1]
The quiet-repository problem
The policy targets a real operational cost: vulnerability alerts accumulate across abandoned experiments, forks and archived work, while detection systems and maintainers have finite attention. But “inactive” and “unused” are different states. A stable library, an internal build tool or a pinned container may receive no commits for a year and still sit in a production dependency chain.
The practical risk is therefore not that GitHub erases a known vulnerability. The announced behavior preserves the alert history. The risk is that teams assume monitoring continues automatically, then discover the pause only when they revisit the repository. If a vulnerability is disclosed during that interval, a paused alerting workflow may not prompt anyone to inspect the dependency.
This is an operational inference from the stated policy, not a claim that every dormant repository is exposed. A repository with no maintained consumers may be a reasonable candidate for less monitoring. A repository that supports a live service needs an explicit owner and an explicit decision about continued alerting.
Who is exempt, and where it applies
GitHub says it will not pause alerts on repositories covered by an enforced security configuration that enables Dependabot alerts. It also excludes repositories in enterprises whose alert policy prevents repository administrators from changing the setting. The change applies to all plans on GitHub.com and GitHub Enterprise Cloud with data residency; it does not apply to GitHub Enterprise Server. [1]
Teams using enterprise controls should verify that the enforcement policy actually covers the repositories they care about. The exemption is tied to an enforced configuration that enables alerts, not merely to the existence of a security policy document. Likewise, GitHub Enterprise Server administrators should not infer that this cloud behavior automatically applies to their own installation.
The Dependabot alerts REST API can help teams inventory and manage individual alerts, but its documented endpoints do not replace checking the enablement policy across repositories. Treat the alert list and the repository configuration as separate data: one describes detected issues, the other whether scanning is enabled. [3]
A practical inventory before the deadline
Start with repositories that have production consumers, published packages, deployment manifests or long-lived release branches. Assign an owner to each. For every repository, decide whether alerts should stay enabled, whether an enforced organization configuration covers it, or whether the project should be retired and its consumers moved.
For repositories that should remain monitored, make a qualifying push or explicitly re-enable alerts before the deadline, then verify the setting in repository configuration. A tiny “keepalive” commit solely to reset activity may be tempting, but it records noise without establishing ownership or proving the code is still supported. Prefer a deliberate maintenance update or an enforced policy that expresses the intended state. This recommendation is editorial guidance based on the activity rules GitHub documented. [1]
For a repository being retired, archive it only after downstream consumers have been checked. Record the replacement, the last supported version and who owns any remaining deployment. Archiving the repository is not what restores Dependabot alerts; GitHub’s announcement says a push or manually re-enabling alerts does that. Keep these actions distinct in internal runbooks.
Finally, make the change visible in security operations. Add a report for repositories whose alert state is disabled or whose owner is unknown. Review that report alongside dependency updates and software inventories, rather than relying on a once-a-year reminder. GitHub’s own docs explain that alerts surface vulnerable dependencies, but they do not decide whether a dormant project still matters to your organization. [2]
The useful takeaway is simple: a year without a push is not a reliable measure of risk. Treat December 8 as an inventory deadline. Decide which quiet repositories are genuinely retired and which still need monitoring, and document that choice before automated alerting goes dark.
Related reading: GitHub’s repository-level AI Scan controls and our guide to GitHub Actions workflow log secret scanning.
Frequently asked questions
When does GitHub begin pausing alerts on inactive repositories?
GitHub says the change starts December 8, 2026. Most repositories without qualifying activity during the prior year will have Dependabot alerts turned off.
Are existing Dependabot alerts deleted when a repository becomes inactive?
No. GitHub says existing alerts are archived rather than deleted. A push or manually re-enabling alerts restores them, and the one-year activity clock starts over.
What activity keeps alerts enabled?
GitHub counts a push to any branch or tag, repository creation, and enabling Dependabot alerts. An enforced security configuration that enables alerts also exempts a repository.



/* Comments */
Comments are offline right now — we reconnect automatically, nothing is lost.