Skip to main content

About Dependabot alerts

GitHub Enterprise Server sends Dependabotアラート when we detect vulnerabilities affecting your repository.

About vulnerable dependencies

脆弱性とは、プロジェクトあるいはそのコードを利用する他のプロジェクトにおいて、秘密性、一貫性、可用性を損なうために悪用されうる、プロジェクトコードの問題です。 脆弱性の種類、重要度、攻撃の方法は様々です。

When your code depends on a package that has a security vulnerability, this vulnerable dependency can cause a range of problems for your project or the people who use it.

Detection of vulnerable dependencies

Dependabot performs a scan to detect vulnerable dependencies and sends Dependabotアラート when:

  • New advisory data is synchronized to your GitHub Enterprise Server instance each hour from For more information about advisory data, see "Browsing security vulnerabilities in the GitHub Advisory Database" in the documentation.

    Note: Only advisories that have been reviewed by GitHub will trigger Dependabotアラート.

  • The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on. For more information, see "About the dependency graph."

加えて、 GitHubは、リポジトリのデフォルトブランチに対して作成されたPull Request中で追加、更新、削除された依存関係のレビューを行うことができ、プロジェクトに脆弱性をもたらすような変更にフラグを立てることができます。 これによって、脆弱な依存関係がコードベースに達したあとではなく、達する前に特定して対処できるようになります。 詳しい情報については「Pull Request中の依存関係の変更のレビュー」を参照してください。

For a list of the ecosystems that GitHub Enterprise Server can detect vulnerabilities and dependencies for, see "Supported package ecosystems."

Note: It is important to keep your manifest and lock files up to date. If the dependency graph doesn't accurately reflect your current dependencies and versions, then you could miss alerts for vulnerable dependencies that you use. You may also get alerts for dependencies that you no longer use.

Dependabotアラート for vulnerable dependencies

Enterprise owners must enable Dependabotアラート for vulnerable dependencies for your GitHub Enterprise Server instance before you can use this feature. For more information, see "Enabling Dependabot for your enterprise."

When GitHub Enterprise Server identifies a vulnerable dependency, we generate a Dependabot alert and display it on the Security tab for the repository and in the repository's dependency graph. The alert includes a link to the affected file in the project, and information about a fixed version. GitHub Enterprise Server may also notify the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "Configuring notifications for vulnerable dependencies."

Note: GitHub Enterprise Server's security features do not claim to catch all vulnerabilities. Though we are always trying to update our vulnerability database and generate alerts with our most up-to-date information, we will not be able to catch everything or tell you about known vulnerabilities within a guaranteed time frame. These features are not substitutes for human review of each dependency for potential vulnerabilities or any other issues, and we recommend consulting with a security service or conducting a thorough vulnerability review when necessary.

Access to Dependabotアラート

You can see all of the alerts that affect a particular project in the repository's dependency graph. For more information, see "Viewing Dependabotアラート for vulnerable dependencies."

By default, we notify people with admin permissions in the affected repositories about new Dependabotアラート.

To receive notifications about Dependabotアラート on repositories, you need to watch these repositories, and subscribe to receive "All Activity" notifications or configure custom settings to include "Security alerts." For more information, see "Configuring your watch settings for an individual repository."

You can choose the delivery method for notifications, as well as the frequency at which the notifications are sent to you. For more information, see "Configuring notifications for vulnerable dependencies."

You can also see all the Dependabotアラート that correspond to a particular vulnerability in the GitHub Advisory Database. For more information about advisory data, see "Browsing security vulnerabilities in the GitHub Advisory Database" in the documentation.