Skip to main content

About Dependabot alerts

GitHub Enterprise Server 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 performs a scan to detect vulnerable dependencies and sends Dependabot 警报 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" 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.

Dependabot 警报 for vulnerable dependencies

Enterprise owners must enable Dependabot 警报 for vulnerable dependencies for 您的 GitHub Enterprise Server 实例 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 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.

Access to Dependabot 警报

You can see all of the alerts that affect a particular project in the repository's dependency graph. For more information, see "Viewing Dependabot 警报 for vulnerable dependencies."

By default, we notify people with admin permissions in the affected repositories about new Dependabot 警报.

要接收有关存储库上 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 about advisory data, see "Browsing security vulnerabilities in the GitHub Advisory Database" in the GitHub.com documentation.