👋 We've unified all of GitHub's product documentation in one place! Check out the content for REST API, GraphQL API, and Developers. Learn more on the GitHub blog.
Article version: Enterprise Server 2.20

About alerts for vulnerable dependencies

GitHub Enterprise sends security alerts when we detect vulnerabilities affecting your repository.

In this article

Were you able to find what you were looking for?

About security vulnerabilities in dependencies

A vulnerability is a problem in a project's code that could be exploited to damage the confidentiality, integrity, or availability of the project or other projects that use its code. Depending on the severity level and the way your project uses the dependency, vulnerabilities can cause a range of problems for your project or the people who use it. You can track and resolve vulnerabilities for certain types of dependencies in your GitHub Enterprise repository.

If GitHub detects a vulnerability from the GitHub Advisory Database or WhiteSource in one of the dependencies in your repository's dependency graph, we'll send you an alert. For more information about the GitHub Advisory Database, see "Browsing security vulnerabilities in the GitHub Advisory Database."

Security alerts for vulnerable dependencies

When a new vulnerability is added to the GitHub Advisory Database, we identify repositories that use the affected version of the dependency and send a security alert to repository maintainers.

Each security alert includes a severity level and a link to the affected file in your project. When available, the alert will include further details about the vulnerability.

You can see all of the alerts affecting a particular project in the repository's dependency graph.

We send security alerts to people with admin permissions in the affected repositories by default. GitHub Enterprise never publicly discloses identified vulnerabilities for any repository.

Your site administrator must enable security alerts for vulnerable dependencies for your GitHub Enterprise Server instance before you can use this feature. For more information, see "Enabling security alerts for vulnerable dependencies on GitHub Enterprise Server."

For a list of the supported languages that GitHub Enterprise can detect vulnerabilities and dependencies for, see "Listing the packages that a repository depends on."

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.

Configuring notifications for security alerts

By default, if your site administrator has configured email for notifications on your instance, you will receive security alerts by email. You can also choose to receive security alerts 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 "Choosing the delivery method for your notifications ."

Email notifications for security alerts 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 security alerts. For more information, see "About email notifications."

Further reading

Were you able to find what you were looking for?

Ask a human

Can't find what you're looking for?

Contact us