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 more information, see About the dependency graph.
When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository.
Enabling the dependency graph for a GitHub Enterprise Server instance
If the dependency graph is not available on your GitHub Enterprise Server instance, ask an enterprise owner to enable it. For more information, see Enabling the dependency graph for your enterprise.
Next steps
You can use the dependency submission API to submit dependencies from the package manager or ecosystem of your choice, even if the ecosystem is not supported by dependency graph for manifest or lock file analysis. Dependencies submitted to a project using the dependency submission API will show which detector was used for their submission and when they were submitted. For more information on the dependency submission API, see Using the dependency submission API.
For more information on viewing the dependency graph, see Exploring the dependencies of a repository.