Understanding your software supply chain

GitHub helps you secure your supply chain, from understanding the dependencies in your environment, to knowing about vulnerabilities in those dependencies, and patching them.

You can use the dependency graph to identify all your project's dependencies. The dependency graph supports a range of popular package ecosystems.

Dependency graph supports a variety of ecosystems.

You can allow users to identify their projects' dependencies by enabling the dependency graph.

You can use automatic dependency submission to submit transitive dependency data in your repository. This enables you to analyze these transitive dependencies using the dependency graph.

You can export a software bill of materials or SBOM for your repository from the dependency graph. SBOMs allow transparency into your open source usage and help expose supply chain vulnerabilities, reducing supply chain risks.

You can use the dependency submission API to submit dependencies for projects, such as the dependencies resolved when a project is built or compiled.

Dependency review lets you catch insecure dependencies before you introduce them to your environment, and provides information on license, dependents, and age of dependencies.

You can use dependency review to catch vulnerabilities before they are added to your project.

Learn how to add a basic customization to your dependency review configuration.

Dependency review lets you catch insecure dependencies before you introduce them to your environment. You can enforce the use of the dependency review action across your organization.

You can use the dependency graph to see the packages your project depends on and the repositories that depend on it. In addition, you can see any vulnerabilities detected in its dependencies.

If the dependency information reported by the dependency graph is not what you expected, there are a number of points to consider, and various things you can check.