Skip to main content

Configuring Dependabot security updates

You can use Dependabotセキュリティアップデート or manual pull requests to easily update vulnerable dependencies.

About configuring Dependabotセキュリティアップデート

You can enable Dependabotセキュリティアップデート for any repository that uses Dependabotアラート and the dependency graph. For more information, see "About Dependabotセキュリティアップデート."

You can disable Dependabotセキュリティアップデート for an individual repository or for all repositories owned by your personal account or organization. For more information, see "Managing Dependabotセキュリティアップデート for your repositories" below.


Supported repositories

GitHub automatically enables Dependabotセキュリティアップデート for every repository that meets these prerequisites.

Note: You can manually enable Dependabotセキュリティアップデート, even if the repository doesn't meet some of the prerequisites below. For example, you can enable Dependabotセキュリティアップデート on a fork, or for a package manager that isn't directly supported by following the instructions in "Managing Dependabotセキュリティアップデート 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"
Dependabotセキュリティアップデート are not disabled for the repository"Managing Dependabotセキュリティアップデート 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 GitHub Support.

Managing Dependabotセキュリティアップデート for your repositories

You can enable or disable Dependabotセキュリティアップデート for an individual repository (see below).

You can also enable or disable Dependabotセキュリティアップデート 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セキュリティアップデート require specific repository settings. For more information, see "Supported repositories."

Enabling or disabling Dependabotセキュリティアップデート for an individual repository

  1. GitHub.comで、リポジトリのメインページにアクセスしてください。

  2. リポジトリ名の下で Settings(設定)をクリックしてください。 リポジトリの設定ボタン

  3. In the "Security" section of the sidebar, click Code security and analysis.

  4. Under "Code security and analysis", to the right of "Dependabot security updates", click Enable to enable the feature or Disable to disable it. For public repositories, the button is disabled if the feature is always enabled. Screenshot of "Code security and analysis" section with button to enable Dependabotセキュリティアップデート

Overriding the default behavior with a configuration file

You can override the default behavior of Dependabotセキュリティアップデート 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 open-pull-request-limit to 0 in order to prevent version updates for a given package-ecosystem. For more information, see "open-pull-request-limit."

# Example configuration file that:
#  - Ignores lodash dependency
#  - Disables version-updates

version: 2
  - package-ecosystem: "npm"
    directory: "/"
      interval: "daily"
      - 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."

Further reading