About alerts for vulnerable dependencies

GitHub 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 detects vulnerable dependencies and sends Dependabotアラート when:

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

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.

Dependabot alerts for vulnerable dependencies

GitHub detects vulnerable dependencies in public repositories and generates Dependabotアラート by default. Owners of private repositories, or people with admin access, can enable Dependabotアラート by enabling the dependency graph and Dependabotアラート for their repositories.

You can also enable or disable Dependabotアラート for all repositories owned by your user account or organization. For more information, see "Managing security and analysis settings for your user account" or "Managing security and analysis settings for your organization."

For information about permission requirements for actions related to Dependabotアラート, see "Repository permission levels for an organization."

GitHub starts generating the dependency graph immediately and generates 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 generate a Dependabot alert and display it on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. GitHub also notifies the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "Configuring notifications for vulnerable dependencies."

For repositories where Dependabotセキュリティアップデート are enabled, the alert may also contain 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 "About Dependabotセキュリティアップデート."

Note: GitHub'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 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."

By default, we notify people with admin permissions in the affected repositories about new Dependabotアラート. GitHub never publicly discloses identified vulnerabilities for any repository. You can also make Dependabotアラート visible to additional people or teams working repositories that you own or have admin permissions for. For more information, see "Managing security and analysis settings for your repository."

Watchしているか、セキュリティアラートをサブスクライブしているリポジトリ上で Dependabotアラートに関する通知の配信方法と頻度を選択できます。 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, see "Browsing security vulnerabilities in the GitHub Advisory Database."

Further reading

このドキュメントは役立ちましたか?プライバシーポリシー

これらのドキュメントを素晴らしいものにするのを手伝ってください!

GitHubのすべてのドキュメントはオープンソースです。間違っていたり、はっきりしないところがありましたか?Pull Requestをお送りください。

コントリビューションを行う

OR, コントリビューションの方法を学んでください。

問題がまだ解決していませんか?

GitHubコミュニティで質問するサポートへの連絡