{% data reusables.dependabot.about-the-dependency-graph %}

When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated.{% ifversion fpt or ghec %} In addition, the graph is updated when anyone pushes a change to the repository of one of your dependencies.{% endif %} For information on the supported ecosystems and manifest files, see "Supported package ecosystems" below.

{% data reusables.dependency-submission.dependency-submission-link %}

When you create a pull request containing changes to dependencies that targets the default branch, {% data variables.product.prodname_dotcom %} 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 "AUTOTITLE."

{% data reusables.dependency-graph.sbom-export %}

{% ifversion fpt or ghec %} {% data reusables.dependency-graph.feature-availability %} For more information, see "AUTOTITLE."

Repository administrators can also set up the dependency graph for private repositories. For more information, see "AUTOTITLE."

{% endif %}

{% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %}

{% ifversion ghes %} For more information about configuration of the dependency graph, see "AUTOTITLE."{% endif %}

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, as well as any dependencies that are submitted using the {% data variables.dependency-submission-api.name %} (beta). This includes:

• Direct dependencies, that are explicitly defined in a manifest or lock file or have been submitted using the {% data variables.dependency-submission-api.name %} (beta)
• Indirect dependencies of these direct dependencies, also known as transitive dependencies or sub-dependencies

The dependency graph identifies indirect dependencies{% ifversion fpt or ghec %} only if they are defined in a lock file or have been submitted using the {% data variables.dependency-submission-api.name %} (beta). For the most reliable graph, you should use lock files (or their equivalent) because they define exactly which versions of the direct and indirect dependencies you currently use. If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}. If your ecosystem does not have lock files, you can use pre-made actions that resolve transitive dependencies for many ecosystems. For more information, see "AUTOTITLE."

For more information on how {% data variables.product.product_name %} helps you understand the dependencies in your environment, see "AUTOTITLE."

{% ifversion fpt or ghec %}

For public repositories, only public repositories that depend on it or on packages that it publishes are reported. This information is not reported for private repositories.{% endif %}

You can use the dependency graph to:

• Explore the repositories your code depends on{% ifversion fpt or ghec %}, and those that depend on it{% endif %}. For more information, see "AUTOTITLE." {% ifversion ghec %}
• View a summary of the dependencies used in your organization's repositories in a single dashboard. For more information, see "AUTOTITLE."{% endif %}
• View and update vulnerable dependencies for your repository. For more information, see "AUTOTITLE."
• See information about vulnerable dependencies in pull requests. For more information, see "AUTOTITLE."

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.{% ifversion fpt or ghec %} Indirect dependencies that are inferred from a manifest file (or equivalent) are excluded from the checks for insecure dependencies.{% endif %}

{% note %}

Notes:

• 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.

{% ifversion github-actions-in-dependency-graph %}

• {% data variables.product.prodname_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[*].steps[*].uses or jobs.<job_id>.uses will be parsed as dependencies. For more information, see "AUTOTITLE."

{% endif %}

• {% data reusables.dependabot.dependabot-alert-actions-semver %} For more information, see "AUTOTITLE" and "AUTOTITLE."

{% endnote %}

You can use the {% data variables.dependency-submission-api.name %} (beta) to add dependencies from the package manager or ecosystem of your choice to the dependency graph, even if the ecosystem is not in the supported ecosystem list above. {% data reusables.dependency-graph.dependency-submission-API-short %}

You will only get {% data variables.product.prodname_dependabot_alerts %} for dependencies that are from one of the supported ecosystems of the {% data variables.product.prodname_advisory_database %}. For more information on the {% data variables.dependency-submission-api.name %}, see "AUTOTITLE."

• "Dependency graph" on Wikipedia
• "AUTOTITLE"
• "AUTOTITLE"
• "AUTOTITLE"