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.
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 GitHub.com. For more information about advisory data, see "Browsing security vulnerabilities in the GitHub Advisory Database" in the GitHub.com 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 可以查看在针对仓库默认分支的拉取请求中添加、更新或删除的任何依赖项，并标记任何将漏洞引入项目的变化。 这允许您在易受攻击的依赖项到达您的代码库之前发现并处理它们，而不是事后处理。 更多信息请参阅“审查拉取请求中的依赖项更改”。
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.
Enterprise owners must enable Dependabot 警报 for vulnerable dependencies for your GitHub Enterprise Server instance before you can use this feature. 更多信息请参阅“在企业帐户上启用依赖关系图和 Dependabot 警报”。
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.
You can see all of the alerts that affect a particular project 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 警报.
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 GitHub.com documentation.