Skip to main content
설명서에 자주 업데이트를 게시하며 이 페이지의 번역이 계속 진행 중일 수 있습니다. 최신 정보는 영어 설명서를 참조하세요.

Dependabot 경고 정보

GitHub Enterprise Server은 리포지토리가 취약한 종속성를 사용하는 것을 감지하면 Dependabot alerts를 보냅니다.

Dependabot alerts은(는) GitHub Enterprise Server의 리포지토리(사용자 소유 및 조직 소유)에 무료로 사용할 수 있습니다. 엔터프라이즈 관리자가 엔터프라이즈에 기능을 사용하도록 설정하는 경우.

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.

For more information, see "Browsing security advisories in the 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. For more information, see "Browsing security advisories in the 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."

Additionally, GitHub can review any dependencies added, updated, or removed in a pull request made against the default branch of a repository, and flag any changes that would reduce the security of your project. This allows you to spot and deal with vulnerable dependencies before, rather than after, they reach your codebase. For more information, see "Reviewing dependency changes in a pull request."

For a list of the ecosystems that GitHub Enterprise Server detects insecure dependencies in, see "About the dependency graph."

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."

For repositories where Dependabot security updates 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 security updates."

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.

To receive notifications about Dependabot alerts 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 notifications."

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 Dependabot alerts."

You can also see all the Dependabot alerts that correspond to a particular advisory in the GitHub Advisory Database. For more information, see "Browsing security advisories in the GitHub Advisory Database."

Further reading