GitHub Dependabot alerts to be automatically turned off for many ‘inactive for 1 year’ repositories starting December 8—Two settings to prevent this for systems that are still running but easily overlooked
What you will learn in this article
-
In a Changelog dated November 10, 2026, GitHub announced that starting December 8, 2026, it will turn off Dependabot alerts (a feature that notifies you of known vulnerabilities in libraries you depend on) for many repositories that have had no activity in the past year. Existing alerts will not be deleted but will be archived and can be restored at any time.
-
The three actions counted as “activity” are: pushing to a branch or tag, creating a repository, and turning on Dependabot alerts. Pushing will automatically turn them back on and restart the one-year countdown.
-
If you do not want to stop the alerts, you can enforce the “security configuration” that enables Dependabot alerts, or use Enterprise policies to prevent repository administrators from turning them on or off, which will exclude them from being turned off. This applies to all plans on github.com and GitHub Enterprise Cloud with data residency; GitHub Enterprise Server is not affected.
“Starting December 8, 2026, GitHub will turn off Dependabot alerts on most repositories with no activity in the past year.”—GitHub wrote this in its November 10, 2026, Changelog titled “Dependabot alerts will pause on inactive repositories” (meaning that from December 8, 2026, GitHub will turn off Dependabot alerts for many repositories that have had no activity in the past year).
Dependabot alerts are a GitHub feature that notifies you when known vulnerabilities are found in libraries used by your repository. GitHub explains the reason for this change as a way to keep Dependabot running quickly and stably for actively developed repositories, given the rapid increase in the volume of vulnerability discoveries and alerts.
On the other hand, “not changing code for a year” is not the same as “not being used.” For old systems that continue to run within a company or repositories with libraries that are no longer updated, there is a possibility that alerts will stop arriving even if new vulnerabilities are found after December 8. This article is intended for those who manage GitHub organizations or repositories at their company, as well as development team leaders, to organize the points to check by December 8 based on the GitHub Changelog and official documentation.
What has been announced—Alerts will be turned off for repositories with no activity for one year starting December 8
According to the Changelog, starting December 8, 2026, GitHub will turn off Dependabot alerts for most repositories that have had no activity in the past year.
Existing alerts will not be deleted
Existing alerts for repositories that have been turned off will not be deleted but will be archived. GitHub explains that archived alerts can be restored at any time.
Affected environments
This change applies to all plans on github.com and GitHub Enterprise Cloud with data residency. If you use data residency, archived alerts will be stored in the same region as other data for that enterprise. It does not apply to GitHub Enterprise Server, which runs on your own servers.
What counts as “activity”—Pushing, creating, and enabling alerts
According to the Changelog, the following three items count as “activity.”
・Pushing to any branch or tag
・Creating a repository
・Turning on Dependabot alerts
How to restore after being turned off
Pushing to a repository will automatically turn Dependabot alerts back on. You can also turn them on manually from the repository settings. In either case, the archived alerts will be restored, and the one-year countdown will restart.
Conditions under which alerts will not be disabled: ‘Enforced security configurations’ and ‘Enterprise policies’
According to the Changelog, alerts will not be disabled even if there is no activity for repositories that meet either of the following criteria (these are the two exceptions cited by the Changelog).
・Repositories where a ‘security configuration’ that enables Dependabot alerts is applied in an ‘enforced’ state
・Enterprise repositories where repository administrators are not permitted to toggle alerts on or off under the Enterprise Dependabot alerts policy
First: Set the security configuration to ‘Enforce’
According to the GitHub documentation ‘Creating a custom security configuration,’ you can create your own security configuration under ‘Configurations’ in the ‘Advanced Security’ section of your organization’s settings. If you enable Dependabot alerts within the configuration and select ‘Enforce configuration’ under the ‘Policy’ section, repository owners will be unable to change the features enabled or disabled by that configuration. A created configuration only takes effect once it is applied to the target repository (the same documentation provides ‘Applying a custom security configuration’ as the next step). The documentation also notes that the enforcement of a security configuration may be lifted in some cases.
Second: Do not allow repository administrators to toggle alerts via Enterprise policy
According to the GitHub Enterprise Cloud documentation, you can choose whether repository administrators can toggle Dependabot alerts on or off under ‘Enable or disable Dependabot alerts by repository admins’ in the ‘Policies’ -> ‘Advanced Security’ section of the Enterprise settings. Note that this policy only affects repository administrators; organization owners and security managers can enable security features regardless of the policy, the documentation states.
An often overlooked perspective: ‘No code changes for one year’ does not mean ‘not in use’
What AI TREND LAB wants to be careful about with this change is that the ‘activity’ counted by GitHub is limited to operations such as pushes to the repository.
For example, the following types of repositories may actually be in use even if the code has not been changed for over a year.
・Business systems that continue to run internally, or small web services like inquiry forms
・Common libraries that are no longer updated but are being loaded by other projects
・Deliverables that have been handed over and published for customers, with no plans for further modifications
In such repositories, new vulnerabilities may be found in dependent libraries even if the code itself has not been changed. If alerts are disabled after December 8, you will no longer receive notifications. AI TREND LAB believes this could lead to a state where you are ‘not aware’ because you haven’t changed anything, rather than being ‘safe’ because you haven’t changed anything.
Implications for those who manage and use GitHub
The following is AI TREND LAB’s analysis based on primary information; please note in advance that it includes speculation rather than definitive statements. Furthermore, AI TREND LAB has not verified this change in actual repositories, and the following is a summary of the official explanation and analysis based on it.
Implication 1 (Analysis): Identify ‘repositories with no pushes for one year’ before December 8
First, you should check how many repositories in your organization have had no pushes in the past year. After that, categorizing them into ‘those that are truly unused’ and ‘those that are still running’ will make it easier to decide whether it is okay to stop the alerts.
Implication 2 (Analysis): Protect running repositories through settings rather than relying on pushes
While one could consider making empty pushes just to restore the alerts, this would require the same task every year, and if forgotten, they would be turned off again. For repositories that are still in use, it is considered easier to manage by enforcing a security configuration that enables Dependabot alerts, as this eliminates the worry of forgetting to push. However, since the documentation also notes that enforcement may be lifted in some cases, it is recommended to verify the status after application as well.
Suggestion 3 (Consideration): Also consider archiving or deleting repositories that are truly no longer in use
Conversely, for repositories that are clearly no longer in use, taking this opportunity to organize them by archiving the repository itself (a different feature from archiving Dependabot alerts) or deleting them will make it easier to keep track of which ones are active.
Summary: Things you can try starting tomorrow
In a Changelog dated November 10, 2026, GitHub announced that starting December 8, 2026, it will turn off Dependabot alerts for many repositories that have had no activity in the past year. Existing alerts will not be deleted but will be archived, and can be restored by pushing or turning them on in the settings. Repositories that enforce a security configuration that enables Dependabot alerts, and Enterprise repositories where the Enterprise policy does not allow repository administrators to turn them on or off, will not be subject to being turned off. This applies to all plans on github.com and GitHub Enterprise Cloud with data residency, but does not apply to GitHub Enterprise Server.
-
Identify repositories with no pushes for one year: Create a list of repositories that are likely to be affected before December 8
-
Separate those that are still in use: Check if there are any systems used within the company or libraries being loaded by others
-
Handle repositories you want to protect with settings: Apply a security configuration that enables Dependabot alerts with “Enforce,” or check your Enterprise policies
For details, please be sure to check the primary sources directly.
Sources
GitHub “Dependabot alerts will pause on inactive repositories” (GitHub Changelog, November 10, 2026)
GitHub “Creating a custom security configuration” (GitHub Docs, confirmed November 12, 2026)
https://docs.github.com/en/code-security/how-tos/secure-at-scale/configure-organization-security/establish-complete-coverage/create-custom-configuration
GitHub “Enforcing policies for code security and analysis for your enterprise” (GitHub Enterprise Cloud Docs, confirmed November 12, 2026)
https://docs.github.com/en/enterprise-cloud@latest/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise
Conclusion
At AI TREND LAB, we carefully verify research, reports, and official announcements released overseas from primary sources, and while avoiding exaggeration or definitive statements, we translate and organize them from the perspective of how Japanese business professionals can apply them to their practical work or side businesses.
Moving forward, AI TREND LAB will continue to provide accurate and easy-to-understand information on the latest AI trends based on primary information from overseas.