Configuring Dependabot security updates

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

Note: Dependabot security and version updates are currently in private beta and subject to change. To request access to the beta release, contact your account management team.

Note: Your site administrator must set up Dependabot updates for your GitHub Enterprise Server instance before you can use this feature. For more information, see "Setting up Dependabot security and version updates on your enterprise."

About configuring Dependabot security updates

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

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

Supported repositories

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

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

Automatic enablement prerequisiteMore information
Repository is not a fork"About forks"
Repository is not archived"Archiving repositories"
Repository contains dependency manifest file from a package ecosystem that GitHub supports"Supported package ecosystems"
Dependabot security updates are not disabled for the repository"Managing Dependabot security updates for your repository"

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 your site administrator.

Managing Dependabot security updates for your repositories

You can enable or disable Dependabot security updates for an individual repository (see below).

You can also enable or disable 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."

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

Enabling or disabling Dependabot security updates for an individual repository

  1. On your GitHub Enterprise Server instance, navigate to the main page of the repository.
  2. Under your repository name, click Settings. Repository settings button
  3. In the left sidebar, click Security & analysis. "Security & analysis" tab in repository settings
  4. Under "Configure security and analysis features", to the right of "Dependabot security updates", click Enable or Disable. "Configure security and analysis features" section with button to enable Dependabot security updates

Further reading

Did this doc help you?

Privacy policy

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.