| title | Enabling the dependency graph | ||||||
|---|---|---|---|---|---|---|---|
| intro | You can allow users to identify their projects' dependencies by enabling the dependency graph. | ||||||
| permissions | {% data reusables.permissions.dependency-graph %} | ||||||
| redirect_from |
|
||||||
| versions |
|
||||||
| shortTitle | Enable dependency graph | ||||||
| contentType | how-tos | ||||||
| category |
|
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 {% data variables.dependency-submission-api.name %}. For more information, see AUTOTITLE.
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{% ifversion fpt or ghec %} and every push to other repositories in the graph{% endif %}.
{% ifversion ghes %}
{% data reusables.dependabot.ghes-enabling-dependency-graph %}
{% else %}
Enabling the dependency graph gives {% data variables.product.github %} read-only access to the dependency manifest and lock files for a repository.
{% data reusables.dependabot.enabling-disabling-dependency-graph-private-repo-public-fork %}
You can enable or disable the dependency graph for all repositories owned by your user account, regardless of their visibility. See AUTOTITLE.
You can also enable the dependency graph for multiple repositories in an organization at the same time. For more information, see {% ifversion security-configurations %}AUTOTITLE.{% else %}AUTOTITLE.{% endif %}
{% endif %}
{% data reusables.dependency-submission.dependency-submission-link %}
For more information on viewing the dependency graph, see AUTOTITLE.
{%- ifversion maven-transitive-dependencies %}