👋 We've unified all of GitHub's product documentation in one place! Check out the content for REST API, GraphQL API, and Developers. Stay tuned for a blog post later today.

記事のバージョン: GitHub.com

About alerts for vulnerable dependencies

GitHub sends GitHub 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

GitHub Dependabot detects vulnerable dependencies and sends Dependabot alerts when:

For a list of the ecosystems that GitHub 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.

GitHub Dependabot alerts for vulnerable dependencies

GitHub detects and alerts users to vulnerable dependencies in public repositories by default. Owners of private repositories, or people with admin access, can enable GitHub Dependabotアラート by enabling the dependency graph and GitHub Dependabotアラート for their repositories. GitHub starts generating the dependency graph immediately and sends alerts for any vulnerable dependencies as soon as they are identified. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. For more information, see "Managing data use settings for your private repository."

When GitHub identifies a vulnerable dependency, we send a Dependabot alert to the maintainers of affected repositories with details of the vulnerability, a link to the affected file in the project, and information about a fixed version. For repositories that have enabled GitHub Dependabotセキュリティアップデート, the alert also contains a link to a pull request to update the manifest or lock file to the minimum version that resolves the vulnerability. For more information, see "Configuring GitHub Dependabotセキュリティアップデート."

Note: GitHub's security features do not claim to catch all vulnerabilities. Though we are always trying to update our vulnerability database and alert you with our most up-to-date information, we will not be able to catch everything or alert you to 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 alerts

You can see all of the alerts that affect a particular project on the repository's Security tab or in the repository's dependency graph. For more information, see "Viewing and updating vulnerable dependencies in your repository."

We send Dependabot alerts to people with admin permissions in the affected repositories by default. GitHub never publicly discloses identified vulnerabilities for any repository. You can also enable Dependabot alerts for additional people or teams working in organization-owned repositories. For more information, see "Managing alerts for vulnerable dependencies in your organization's repositories."

Configuring notifications for GitHub Dependabotアラート

By default, you will receive GitHub Dependabotアラート by email, grouped by the specific vulnerability. You can also choose to receive GitHub Dependabotアラート in a weekly email summarizing alerts for up to 10 of your repositories, in your web notifications, or in the GitHub user interface. For more information, see "Configuring notifications."

1つ以上のリポジトリに影響するセキュリティアラートに関するメール通知には、X-GitHub-Severityヘッダフィールドが含まれます。 X-GitHub-Severityヘッダフィールドの値を使って、セキュリティアラートのメール通知をフィルタリングできます。 For more information, see "Configuring notifications."

Further reading