About the dependency graph
The dependency graph is a summary of the manifest and lock files stored in a repository and any dependencies that are submitted for the repository using the dependency submission API. For each repository, it shows dependencies, the ecosystems and packages it depends on.
For each dependency, you can see the version, the manifest file which included it, and whether it has known vulnerabilities. For package ecosystems supporting transitive dependencies, the relationship status will be displayed and you can click "", then "Show paths", to see the transitive path which brought in the dependency.
You can also search for a specific dependency using the search bar. Dependencies are sorted automatically with vulnerable packages at the top.
GitHub does not retrieve license information for dependencies, and does not calculate information about dependents, the repositories and packages that depend on a repository.
For information on the supported ecosystems and manifest files, see Dependency graph supported package ecosystems.
When you create a pull request containing changes to dependencies that targets the default branch, GitHub uses the dependency graph to add dependency reviews to the pull request. These indicate whether the dependencies contain vulnerabilities and, if so, the version of the dependency in which the vulnerability was fixed. For more information, see About dependency review.
How the dependency graph is built
The dependency graph automatically parses dependencies by analyzing manifests and lock files in your repository. You can also submit data yourself. For more information, see How the dependency graph recognizes dependencies.
Dependency graph availability
Enterprise owners can configure the dependency graph and Dependabot alerts for an enterprise. For more information, see Enabling the dependency graph for your enterprise and Enabling Dependabot for your enterprise.
For more information about configuration of the dependency graph, see Enabling the dependency graph.
What you can do with the dependency graph
You can use the dependency graph to:
- Explore the repositories your code depends on. For more information, see Exploring the dependencies of a repository.
- View and update vulnerable dependencies for your repository. For more information, see About Dependabot alerts.
- See information about vulnerable dependencies in pull requests. For more information, see Reviewing dependency changes in a pull request.
- Export a software bill of materials (SBOM) for audit or compliance purposes. This is a formal, machine-readable inventory of a project's dependencies. See Exporting a software bill of materials for your repository.