Listing the packages that a repository depends on
You can see your project's dependencies, as well as any detected vulnerabilities, in the dependency graph.
In this article
- About the dependency graph
- Supported package ecosystems
- Listing dependencies for a repository with the dependency graph enabled
- Troubleshooting the dependency graph
- Further reading
About the dependency graph
The dependency graph is available for every repository that define dependencies in a supported package ecosystem using a supported file format.
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."
You can view and update vulnerable dependencies in your repository's dependency graph. The dependency graph lists vulnerable dependencies before other dependencies. For more information, see "About security alerts for vulnerable dependencies."
Supported package ecosystems
|Package manager||Languages||Recommended formats||Supported formats|
||.NET languages (C#, C++, F#, VB)||
Note: If you list your Python dependencies within a
setup.py file, we may not be able to parse, list, and alert on every dependency in your project.
Listing dependencies for a repository with the dependency graph enabled
On GitHub Enterprise, navigate to the main page of the repository.
Under your repository name, click Insights.
In the left sidebar, click Dependency graph.
Troubleshooting the dependency graph
If your project has dependencies, but no dependencies are detected in your graph, there may be a problem with the file containing your dependencies. Check your project's file to ensure that it's correctly formatted for the file type.