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.

Dependabot and all related features are covered by your license agreement. For more information, see "GitHub Enterprise Customer Terms."

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. "Code security and analysis" section with button to enable Dependabotセキュリティアップデート

Further reading