# Enabling the dependency graph
You can allow users to identify their projects' dependencies by enabling the dependency graph.
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 [Dependency graph](/en/code-security/concepts/supply-chain-security/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 and every push to other repositories in the graph.
## Enabling the dependency graph for a repository
Enabling the dependency graph gives GitHub read-only access to the dependency manifest and lock files for a repository.
1. On GitHub, navigate to the main page of the repository.
2. Under your repository name, click ** Settings**. If you cannot see the "Settings" tab, select the **** dropdown menu, then click **Settings**.
3. In the "Security and quality" section of the sidebar, click ** Advanced Security**.
4. Read the message about granting GitHub read-only access to the repository data to enable the dependency graph, then next to "Dependency Graph", click **Enable**.
You can disable the dependency graph at any time by clicking **Disable** next to "Dependency Graph" on the settings page for "Advanced Security".
## Enabling the dependency graph for multiple repositories
You can enable or disable the dependency graph for all repositories owned by your user account, regardless of their visibility. See [Managing security and analysis features](/en/account-and-profile/how-tos/account-settings/managing-security-and-analysis-features).
You can also enable the dependency graph for multiple repositories in an organization at the same time. For more information, see [Configuring security features in your organization](/en/code-security/how-tos/secure-at-scale/configure-organization-security).
## 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](/en/code-security/how-tos/secure-your-supply-chain/secure-your-dependencies/use-dependency-submission-api).
For more information on viewing the dependency graph, see [Exploring the dependencies of a repository](/en/code-security/how-tos/secure-your-supply-chain/secure-your-dependencies/explore-dependencies).
## Further reading
* [Configuring automatic dependency submission for your repository](/en/code-security/how-tos/secure-your-supply-chain/secure-your-dependencies/submit-dependencies-automatically)
* [Viewing insights for dependencies in your organization](/en/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-dependencies-in-your-organization)
* [Viewing and updating Dependabot alerts](/en/code-security/how-tos/manage-security-alerts/manage-dependabot-alerts/view-dependabot-alerts)
* [Vulnerable dependency detection](/en/code-security/reference/supply-chain-security/troubleshoot-dependabot/vulnerability-detection)