The Wayback Machine - https://web.archive.org./web/20201102090637/https://docs.github.com/en/free-pro-team@latest/github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates

Configuring GitHub Dependabot security updates

You can use GitHub Dependabot security updates or manual pull requests to easily update vulnerable dependencies.

In this article

Did this doc help you?

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.

About configuring GitHub Dependabot security updates

You can enable GitHub Dependabot security updates for any repository that uses Dependabot alerts and the dependency graph. For more information, see "About GitHub Dependabot security updates."

You can disable GitHub Dependabot security updates for an individual repository or for all repositories owned by your user account or organization. For more information, see "Managing GitHub Dependabot security updates for your repositories" below.

GitHub Dependabot and all related features are covered by GitHub's Terms of Service.

Supported repositories

GitHub automatically enables GitHub Dependabot security updates for every repository that meets these prerequisites.

Note: You can manually enable GitHub Dependabot security updates, even if the repository doesn't meet some of the prerequisites below. For example, you can enable GitHub Dependabot security updates on a fork, or for a package manager that isn't directly supported by following the instructions in "Managing GitHub Dependabot security updates for your repositories."

Automatic enablement prerequisiteMore information
Repository is not a fork"About forks"
Repository is not archived"Archiving repositories"
Repository is public, or repository is private and you have enabled read-only analysis by GitHub, dependency graph, and vulnerability alerts in the repository's settings"Managing data use settings for your private repository."
Repository contains dependency manifest file from a package ecosystem that GitHub supports"Supported package ecosystems"
GitHub Dependabot security updates are not disabled for the repository"Managing GitHub Dependabot security updates for your repository"
Repository is not already using an integration for dependency management"About integrations"

If security updates are not enabled for your repository and you don't know why, first try enabling them using the instructions given in the procedural sections below. If security updates are still not working, you can contact support.

Managing GitHub Dependabot security updates for your repositories

You can enable or disable GitHub Dependabot security updates for an individual repository.

You can also enable or disable GitHub Dependabot security updates for all repositories owned by your user account or organization. For more information, see "Managing security and analysis settings for your user account" or "Managing security and analysis settings for your organization."

GitHub Dependabot security updates require specific repository settings. For more information, see "Supported repositories."

  1. On GitHub, navigate to the main page of the repository.
  2. Under your repository name, click Security.
    Security tab
  3. In the security sidebar, click Dependabot alerts.
    Dependabot alerts tab
  4. Above the list of alerts, use the drop-down menu and select or unselect Dependabot security updates.
    Drop-down menu with the option to enable GitHub Dependabot security updates

Further reading

Did this doc help you?

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.