Note: Dependabot security and version updates are currently in public beta and subject to change.
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 "Enabling Dependabot for your enterprise."
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 personal account or organization. For more information, see "Managing Dependabot security updates for your repositories" below.
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 prerequisite||More 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.
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 personal account or organization. For more information, see "Managing security and analysis settings for your personal account" or "Managing security and analysis settings for your organization."
Dependabot security updates require specific repository settings. For more information, see "Supported repositories."
On your GitHub Enterprise Server instance, navigate to the main page of the repository.
Under your repository name, click Settings.
In the left sidebar, click Security & analysis.
Under "Code security and analysis", to the right of "Dependabot security updates", click Enable to enable the feature or Disable to disable it.
You can override the default behavior of Dependabot security updates by adding a dependabot.yml file to your repository. For more information, see "Configuration options for the dependabot.yml file."
If you only require security updates and want to exclude version updates, you can set
0 in order to prevent version updates for a given
package-ecosystem. For more information, see "
# Example configuration file that: # - Ignores lodash dependency # - Disables version-updates version: 2 updates: - package-ecosystem: "npm" directory: "/" schedule: interval: "daily" ignore: - dependency-name: "lodash" # For Lodash, ignore all updates # Disable version updates for npm dependencies open-pull-requests-limit: 0
For more information about the configuration options available for security updates, see the table in "Configuration options for the dependabot.yml file."