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 for per-package details.