MSRXMSRXSecurity
Tools / Vulnerabilities

Dependency vulnerability scanner

Drop in a lockfile (npm, yarn, pnpm, pip, Poetry, uv, Go, Cargo, Ruby, Composer, Maven, NuGet) and see every package with a known vulnerability, what is being exploited, and the version that fixes it.

Browser + public API

Loading tool…

Good to know

  • Use the lockfile, not the manifest: package.json says ^4.17 while package-lock.json says exactly which 4.17.x is installed.
  • Fix “exploited” packages first, then critical and high. A vulnerable dev-only package matters less than one shipped to production, but still matters in CI.
  • Data comes from OSV.dev, which merges GitHub, PyPI, Go, RustSec and other advisory databases. Add a scanner such as osv-scanner or npm audit to CI so this runs on every change.