# Dependency Analysis ## Overview Nullify continuously monitors every package dependency for known CVEs and determines how risky they are within the context of your application and where it runs. It reviews all packages on your default branch periodically to catch new CVEs as they emerge, and analyzes every pull request to prevent new CVEs from being introduced. This combines vulnerability detection with application context to separate noise from genuine risk. ## What It Delivers * **Manifest discovery** across `go.mod`, `package.json`, `pnpm-lock.yaml`, `yarn.lock`, `bun.lock`, `pom.xml`, `build.gradle`, `libs.versions.toml`, `requirements.txt`, `pyproject.toml`, `conda-lock.yml`, `Gemfile`, `.csproj`, `composer.json`, `Cargo.toml`, and more. * **Enriched advisories** that blend NVD, OSV, vendor feeds, and Nullify intelligence to calculate severity, exploitability, and affected services. * **Reachability reasoning** analyse how your programs use the vulnberable code in the dependency, not just whether it is called, and how exposed it is in the infrastructure. * **Comprehensive triage** compute a risk score comprised of technical and business context * **Automated remediation** for Go modules, npm/Yarn/pnpm, Bun, Maven, Gradle, PyPI/Conda, Composer, and Bundler with changelog summaries and optional PR creation. See [Supported Ecosystems](/capabilities/code-reviews/dependency-analysis/supported-ecosystems.md) for per-package details. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.nullify.ai/capabilities/code-reviews/dependency-analysis.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.