Security & supply chain

Dependabot alerts will go quiet on repos with no activity in a year

Dependabot alerts will go quiet on repos with no activity in a year

Starting December 8, 2026, GitHub will turn off Dependabot alerts on most repositories that have seen no activity in the past year. For security owners, that means the repos nobody touches will also stop reporting new vulnerable dependencies. The change covers every plan on github.com and GitHub Enterprise Cloud with data residency. GitHub Enterprise Server is not affected, per the GitHub Changelog.

The rule as written

GitHub counts three things as activity:

  • a push to any branch or tag
  • creating the repository
  • turning on Dependabot alerts

If none of those has happened in the past year, alerts get paused. Existing alerts are archived. They are not deleted and can be restored at any time. For data residency customers, archived alerts stay in the same region.

Turning alerting back on takes very little. Per the changelog, any push to the repository turns Dependabot alerts back on automatically. An admin can also re-enable them in repository settings, which restores the archived alerts and resets the one-year inactivity clock.

Two groups are exempt. Repositories with an enforced security configuration that enables Dependabot alerts keep alerting. So do repositories under enterprise-level policies that stop administrators from turning alerts off.

Where the gap opens

GitHub's rule assumes that no pushes means nobody cares. In operations that is often wrong. Plenty of repositories are finished: a small internal service that has run untouched since its last deploy, a shared action other workflows call with uses:, a base-image build that only runs when someone remembers it. Those repos produce nothing new, but their dependency tree still ships every time something consumes them.

The CVE feed keeps updating whether or not anyone pushes. A vulnerability disclosed against a pinned transitive dependency in one of those repos is exactly what Dependabot alerts are for. After December 8, the dormant repo will not raise that alert. No error, no failed job. The finding just never appears in anyone's queue.

The archive is reassuring, since nothing already reported is lost. But the risk comes from alerts that never get created, and archiving does nothing about those.

What to do before December 8

The exemption is the fix GitHub is pointing at. If your organization relies on Dependabot alerts as its vulnerability signal, apply a security configuration that enables Dependabot alerts and enforce it. Then the activity check stops mattering for every repo the configuration covers.

Before that, find out which repos are affected. The gh CLI can list repositories with their last push time:

gh repo list "$ORG" --limit 1000 \
  --json name,pushedAt,isArchived \
  --jq '.[] | select(.isArchived | not) | select(.pushedAt < "<cutoff-iso-date>") | .name'

Set <cutoff-iso-date> to one year before your check. Treat the output as an approximation. The last push time does not capture the other two activity triggers, so it can list repos that GitHub still treats as active.

Do not add empty commits to keep repos "active". It works, since any push turns alerts back on, but now a cron job owns your alert coverage, and that cron job is one more thing that can fail silently.

A note on scheduled scans

A common fallback is a scheduled CI job that runs an open-source scanner such as OSV-Scanner, Trivy or Grype against each repo's lockfiles. That approach doesn't depend on Dependabot's activity rule, and the findings land wherever you route them. It has the same weak spot in a different place, though. On GitHub Actions, scheduled workflows in public repositories are disabled automatically after 60 days without repository activity. A scanner that lives inside the dormant repo can go quiet too.

The more durable setup runs the scan centrally, from a repository that is active, against the dormant ones. Or it puts coverage under a policy that an inactivity timer can't override, which is what the enforced-configuration exemption does on GitHub.

Repos that stay below the one-year line keep alerting as they do today. GitHub Enterprise Server is not affected.

Source: GitHub Changelog (github.blog)

Related
Security & supply chain

FakeGit floods GitHub with malicious repos aimed at coding agents

Island researchers say a campaign called FakeGit spun up about 7,600 malicious GitHub repositories, many posing as AI skills or MCP servers, to hand SmartLoader and StealC to developers and to the agents fetching capabilities on their behalf.

July 24, 2026
Developer experience

GitHub's Dependabot playbook: group the version PRs, slow the cadence, keep security fast

A GitHub blog post dated 2026-07-29 lays out the three-lever config for making Dependabot survivable on a busy repo: group version updates into one PR, slow the schedule to weekly or monthly, and let security updates keep flowing on their own timing. It is a few lines of YAML that turn a bot most teams half-mute back into something they can triage.

August 14, 2026
Supply chain security

Dependabot learns to wait: version-update PRs now sit for three days by default

GitHub is flipping Dependabot version updates to a default three-day package cooldown. A new release has to sit on its registry for at least three days before Dependabot will open a version-update PR; security updates are exempt and still open immediately.

July 15, 2026

Turn this into your pipeline. Build it on Buddy.

Start free