About vulnerable dependencies
脆弱性とは、プロジェクトあるいはそのコードを利用する他のプロジェクトにおいて、秘密性、一貫性、可用性を損なうために悪用されうる、プロジェクトコードの問題です。 Vulnerabilities vary in type, severity, and method of attack.
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:
- New advisory data is synchronized to GitHub Enterprise Server each hour from GitHub.com. For more information about advisory data, see "Browsing security vulnerabilities in the GitHub Advisory Database."
- 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."
For a list of the ecosystems that GitHub Enterprise 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
Your site administrator must enable Dependabot alerts for vulnerable dependencies for GitHub Enterprise Server インスタンス before you can use this feature. For more information, see "Enabling alerts for vulnerable dependencies on GitHub Enterprise Server."
When GitHub Enterprise 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.
Note: GitHub Enterprise'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 in the repository's dependency graph.
We send Dependabot alerts to people with admin permissions in the affected repositories by default. GitHub Enterprise never publicly discloses identified vulnerabilities for any repository.
Configuring notifications for GitHub Dependabotアラート
By default, if your site administrator has configured email for notifications on your instance, you will receive GitHub Dependabotアラート by email. 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 Enterprise user interface. For more information, see "Configuring notifications."
Site administrators can also enable GitHub Dependabotアラート without notifications. For more information, see "Enabling Dependabot alerts for vulnerable dependencies on GitHub Enterprise Server."
Email notifications for GitHub Dependabotアラート that affect one or more repositories include the X-GitHub-Severity header field. You can use the value of the X-GitHub-Severity header field to filter email notifications for GitHub Dependabotアラート. For more information, see "Configuring notifications."