About managing vulnerable dependencies

GitHub Enterprise Server helps you to avoid using third-party software that contains known vulnerabilities.

GitHub Enterprise Server provides the following tools for removing and avoiding vulnerable dependencies.

Dependency graph

The dependency graph is a summary of the manifest and lock files stored in a repository. It shows you the ecosystems and packages your codebase depends on (its dependencies) and the repositories and packages that depend on your project (its dependents). The information in the dependency graph is used by dependency review and Dependabot. For more information, see "About the dependency graph."

Dependency review

Note: Dependency review is currently in beta and subject to change.

By checking the dependency reviews on pull requests you can avoid introducing vulnerabilities from dependencies into your codebase. If the pull requests adds a vulnerable dependency, or changes a dependency to a vulnerable version, this is highlighted in the dependency review. You can change the dependency to a patched version before merging the pull request. For more information, see "About dependency review."

Dependabot alerts

GitHub Enterprise Server can create Dependabot alerts when it detects vulnerable dependencies in your repository. The alert is displayed on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. GitHub Enterprise Server also notifies the maintainers of the repository, according to their notification preferences. For more information, see "About alerts for vulnerable dependencies."

Did this doc help you?

Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.