About Dependabot alerts
Dependabot alerts tell you that your code depends on a package that is insecure.
If your code depends on a package with a security vulnerability, this can cause a range of problems for your project or the people who use it. You should upgrade to a secure version of the package as soon as possible.
有关详细信息，请参阅“在 GitHub Advisory Database 中浏览安全公告”。
Detection of insecure dependencies
Dependabot performs a scan to detect insecure dependencies, and sends Dependabot alerts when:
-
New advisory data is synchronized to your GitHub Enterprise Server instance each hour from GitHub.com. 有关详细信息，请参阅“在 GitHub Advisory Database 中浏览安全公告”。
Note: Only advisories that have been reviewed by GitHub will trigger Dependabot alerts.
-
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 detects insecure dependencies in, 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 insecure dependencies that you use. You may also get alerts for dependencies that you no longer use.
Configuration of Dependabot alerts
Enterprise owners must enable Dependabot alerts 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 Dependabot alerts."
Note: GitHub Enterprise Server's security features do not claim to catch all vulnerabilities. We actively maintain GitHub Advisory Database and generate alerts with the most up-to-date information. However, we cannot 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 dependency 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. For more information, see "Viewing and updating Dependabot alerts."
By default, we notify people with admin permissions in the affected repositories about new Dependabot alerts.
若要在存储库上接收有关 Dependabot alerts 的通知，需要监视这些存储库，并订阅以接收“所有活动”通知或配置自定义设置以包括“安全警报”。 有关详细信息，请参阅“为单个存储库配置监视设置”。
可以选择通知的� 递方法，以及通知发送给� 的频率。 For more information, see "Configuring notifications for Dependabot alerts."
You can also see all the Dependabot alerts that correspond to a particular advisory in the GitHub Advisory Database. 有关详细信息，请参阅“在 GitHub Advisory Database 中浏览安全公告”。