What is the purpose of the Dependency Graph?

• A. Monitor known issues within dependencies that may affect the security of your application.
• B. Track code quality issues across branches.
• C. Manage user permissions for repositories.
• D. Monitor deployment statuses across environments.

Answer: (A)

The Dependency Graph is about visibility into the libraries and packages your project uses, including transitive dependencies, so you can spot security issues in those dependencies. By mapping exactly which versions of which packages your code relies on, it lets GitHub correlate any known vulnerabilities with your specific setup. This enables security alerts and automated fixes through Dependabot, helping you remediate vulnerabilities in third‑party code before they can be exploited. It isn’t about tracking code quality, managing repository permissions, or monitoring deployment statuses, which is why those options don’t fit.