GitHub will pause Dependabot alerts on repositories inactive for a year, starting December 8
With vulnerability discovery and alert volume growing fast, GitHub is cutting load from inactive repositories. Which ones are affected and how to turn alerts back on.
// Key points
- Starting December 8, 2026, GitHub will turn off Dependabot alerts on most repositories with no activity in the past year; existing alerts are archived, not deleted, and can be restored at any time.
- Any push turns alerts back on automatically and restores the archived alerts, restarting the one-year clock; alerts can also be re-enabled manually.
- GitHub says vulnerability discovery and alert volume are growing quickly, and the change keeps Dependabot fast and reliable for actively developed repositories.
- It applies to all plans on github.com and to GitHub Enterprise Cloud with data residency, not to GitHub Enterprise Server.
Builder's take"Inactive" does not mean "unused": many teams have internal SDKs or deploy-script repos untouched for a year that production still depends on. Before December 8 I would list those and either re-enable alerts or confirm they are archived and no longer referenced. With models like Carbon and GPT-6 Cyber finding bugs faster, alerts will only grow; do not let old repos you still rely on drop out of sight.
// Background · from #Coding agents
Full timeline →- Nov 11 Gemini 4 Carbon opens to all developers at Argon's introductory price of $2 input and $10 output per million tokens
- Nov 11 NVIDIA donates Agent Substrate to the CNCF Sandbox: idle agent sessions are snapshotted with memory and filesystem, at 10x the density of standard containers
- Nov 10 Anthropic releases Claude Fable 5.2 and Mythos 5.2 at $8 input and $40 output per million tokens, scoring 49.1% on FrontierCode 2.0