👋 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: GitHub.com

About alerts for vulnerable dependencies

GitHub sends GitHub Dependabot 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 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."

GitHub Dependabot alerts and security updates for vulnerable dependencies

When a new vulnerability is added to the GitHub Advisory Database, we identify public repositories (and private repositories that have opted in to vulnerability detection) that use the affected version of the dependency, send a GitHub Dependabot alert to repository maintainers, and generate a GitHub Dependabot security update.

Each Dependabot alert includes a severity level, a link to the affected file in your project, and a link to a pull request containing a security update that resolves the vulnerability. When available, the alert will include further details about the vulnerability.

You can see all of the alerts affecting a particular project on the repository's Security tab or in the repository's dependency graph. For more information, see "Viewing and updating vulnerable dependencies in your repository."

We send Dependabot alerts to people with admin permissions in the affected repositories by default. GitHub never publicly discloses identified vulnerabilities for any repository. You can also enable Dependabot alerts for additional people or teams working in organization-owned repositories. For more information, see "Managing alerts for vulnerable dependencies in your organization's repositories."

GitHub Dependabot security updates update vulnerable dependencies to the minimum version that resolves the vulnerability. Security updates are automatically enabled in repositories that use the dependency graph and GitHub Dependabot alerts, but you can choose to disable automatic pull requests and generate security updates manually instead. For more information, see "Configuring GitHub Dependabot security updates."

GitHub detects and alerts on vulnerable dependencies in public repositories by default. To receive GitHub Dependabot alerts for vulnerable dependencies in a private repository, an owner of or person with admin access to the repository must enable the dependency graph and GitHub Dependabot alerts in the repository. For more information, see "Managing data use settings for your private repository."

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

Note: GitHub'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 GitHub Dependabot alerts

By default, you will receive GitHub Dependabot alerts by email, grouped by the specific vulnerability. You can also choose to receive GitHub Dependabot alerts in a weekly email summarizing alerts for up to 10 of your repositories, in your web notifications, or in the GitHub user interface. For more information, see Configuring notifications ."

Email notifications for GitHub Dependabot 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 GitHub Dependabot alerts. For more information, see "Configuring 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