Your Quiet GitHub Repository May Still Need Security Alerts

An old project can be quiet on GitHub and busy everywhere else. A booking form, dashboard or small website might keep serving people long after its last code change. That makes a new GitHub announcement worth checking before December, even if you are not planning any development.
What's changing
GitHub announced on November 10 that, starting December 8, 2026, Dependabot alerts will turn off on most repositories with no qualifying activity for a year. Existing alerts will be archived, not deleted. Creating a repository, enabling alerts or pushing to any branch or tag counts as activity. A subsequent push automatically re-enables alerts; you can also enable them in settings. Archived alerts return and the one-year timer restarts. GitHub's announcement
The change covers GitHub.com plans and Enterprise Cloud with data residency, not GitHub Enterprise Server. Repositories covered by enforced security configurations enabling alerts, or enterprise alert policies that prevent repository administrators changing the setting, are exceptions. This is a change to vulnerability alerts, not an announcement that old repositories will be deleted. GitHub's scope and exceptions
Start with what is still running
Our suggestion is a small inventory rather than a frantic round of commits. Give each quiet repository one of three labels in your own tracking document: still in service, reference only, or retirement pending. The first means somebody relies on the application. The second means it is kept for learning or historical use. The third means it should be shut down, but that work is not finished.
For anything still in service, record its public address or deployment location, its owner and the last time somebody tested it. A repository name alone is surprisingly poor evidence of what a business still depends on.
Then review its alerts setting. GitHub's configuration instructions explain repository and organization controls. Dependabot alerts identify vulnerable dependencies; receiving an alert is not the same as installing and testing a fix.
Don't confuse activity with maintenance
A tiny cosmetic commit might make a project look active without making it safer. We would rather see a named owner, a repeatable dependency review and a way to restore the application if an update breaks it.
For example, imagine a community group's old sign-up form. The useful job is not changing its footer date. It is finding out who can update the form, whether it still works and how a dependency change would be tested before volunteers rely on it again.
Give the inventory a next-review date, too. Otherwise, today's sensible check becomes next year's forgotten spreadsheet. Put the reminder with the people responsible for the service, not solely with the person who happened to create its repository.
The Butler's take
Quiet code is not necessarily abandoned code. Use this announcement to reconnect old software with an actual maintainer. Never treat an empty notification inbox as proof that a still-running application needs no attention. For a related way to judge tooling by finished outcomes, see our practical workflow-measurement guide.