About the dependency graph
The dependency graph is a summary of the manifest and lock files stored in a repository. For each repository, it shows dependencies, that is, the ecosystems and packages it depends on.
GitHub Enterprise Server does not calculate information about dependents, the repositories and packages that depend on a repository.
When you push a commit to GitHub Enterprise Server that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated. For information on the supported ecosystems and manifest files, see "Supported package ecosystems" below.
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."
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 "Configuring the dependency graph."
The dependency graph includes all the dependencies of a repository that are detailed in the manifest and lock files, or their equivalent, for supported ecosystems. This includes:
- Direct dependencies, that are explicitly defined in a manifest or lock file
- Indirect dependencies of these direct dependencies, also known as transitive dependencies or sub-dependencies
The dependency graph identifies indirect dependencies from the lock files.
For more information on how GitHub Enterprise Server helps you understand the dependencies in your environment, see "About supply chain security."
Using 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."
Supported package ecosystems
The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.
|Package manager||Languages||Recommended formats||All supported formats|
|NuGet||.NET languages (C#, F#, VB), C++|
|GitHub Actions workflows ||YAML|
Note: This feature was unavailable in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The feature is available in 3.5.4 and later. For more information about upgrades, contact your site administrator.
For more information about determining the version of GitHub Enterprise Server you're using, see "About versions of GitHub Docs."
GitHub Actions workflows must be located in the
.github/workflows/ directory of a repository to be recognized as manifests. Any actions or workflows referenced using the syntax
jobs.<job_id>.uses will be parsed as dependencies. For more information, see "Workflow syntax for GitHub Actions."
 If you list your Python dependencies within a
setup.py file, we may not be able to parse and list every dependency in your project.
Note: GitHub Actions workflow dependencies are displayed in the dependency graph for informational purposes. Dependabot alerts are not currently supported for GitHub Actions workflows.