Dependabot Will Pause Alerts on Inactive Repositories: Prevent Security Blind Spots

GitHub will pause Dependabot alerts on December 8, 2026 for most repositories with no activity during the previous year. Existing alerts are archived rather than deleted, but stopping analysis on apparently inactive repositories can create blind spots in legacy applications that still run in production.

What GitHub counts as activity

  • A push to any branch or tag.
  • Repository creation.
  • Turning on Dependabot alerts.

A later push turns alerts back on, restores archived alerts, and restarts the one-year clock.

Repositories that remain protected

GitHub will keep alerts enabled when an enforced security configuration enables Dependabot. Enterprises whose policy prevents repository administrators from enabling or disabling alerts are also excluded. The change applies to all GitHub.com plans and GitHub Enterprise Cloud with data residency; it does not apply to GitHub Enterprise Server.

Why architects and security teams should care

Git activity is not the same as operational relevance. A repository can receive no commits for a year while still producing a container image, Function App, API, internal tool, or library used in production. If Dependabot pauses, newly disclosed dependency vulnerabilities may disappear from the normal remediation workflow.

Actions before December 8

  1. Inventory repositories with no commits in the last twelve months and map them to active workloads, artifacts, and downstream dependencies.
  2. Separate genuinely retired repositories from legacy code that is still deployed or consumed.
  3. Apply an enforced security configuration that enables Dependabot to repositories requiring continuous monitoring.
  4. Assign an owner, criticality, and review cycle to each legacy repository.
  5. Check exports, dashboards, and automations that might interpret archived alerts as remediated vulnerabilities.

Do not use artificial commits as governance

Periodic empty commits may reset the clock, but they are not a durable control. The sustainable approach is an organization- or enterprise-enforced security configuration backed by application inventory and clear ownership.

Recommended governance pattern

  • Tier 1: code producing production workloads or components; enforced configuration with alerts always enabled.
  • Tier 2: internal tools or low-frequency applications; Dependabot enabled with quarterly review.
  • Tier 3: retired repositories; formally archive them, remove deployments, and document retention.

Related reading

If your pipelines use GitHub-hosted runners, also review GitHub Actions Multi-Cloud Runners: Update Allowlists and Entra.

Official references

Leave a Comment