Check your lockfile for vulnerable dependencies

Drop a lockfile and we check every package version against OSV.dev, the open vulnerability database. You get the report by email: what is affected, how to fix it, and a ready-made prompt for your coding agent. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

How it works

  1. You drop or paste a lockfile. We read the exact name and version of every package in it, including indirect (transitive) dependencies. The file itself is not kept.
  2. We check each version against OSV.dev. Versions checked in the last 24 hours come from our shared catalog; the others are looked up in OSV.dev right away.
  3. We group what we find per package. One upgrade usually fixes every advisory of a package, so the report gives you the version to move to, not a list of CVEs to work through.
  4. The report arrives in your inbox in a minute or two, with the commands for your package manager and a prompt you can paste into Claude Code, Cursor or another coding agent.

What the report looks like

Each vulnerable package gets its severity, the advisories that affect it, the version that fixes all of them and the command to upgrade. A shortened, made-up example for a package-lock.json:

High example-http-client 2.3.0

2 advisories, each with its CVE id and a link to the details. Fixed in 2.4.1.

npm install example-http-client@2.4.1
# if it is an indirect dependency: npm update example-http-client (or npm audit fix)

Then: run your tests, commit the updated lockfile.

At the end there is a prompt for your coding agent that lists every package, the target version and how to handle indirect dependencies, so the upgrade can be done in one go. When nothing is affected, you get a short email saying so.

Why a lockfile, and not package.json

A vulnerability affects exact versions: lodash 4.17.20 is affected, 4.17.21 is not. Files like package.json, pyproject.toml, Gemfile or Cargo.toml usually say what you accept (^4.17.0, >=2.28), not what you install. The lockfile next to them records the versions that were actually installed, for your own packages and for everything they pull in.

  • npm, Yarn, pnpm: package-lock.json, yarn.lock, pnpm-lock.yaml.
  • Python: poetry.lock, uv.lock, Pipfile.lock, or a requirements.txt with pinned versions (pip freeze > requirements.txt makes one).
  • Go: go.mod. Rust: Cargo.lock. Ruby: Gemfile.lock. PHP: composer.lock.

Reading the severity

Severities come from the advisory, usually as a CVSS score: critical (9.0 to 10) and high (7.0 to 8.9) are worth fixing today, especially in packages your app uses on every request. Medium and low often need a specific setup to be exploited: read the advisory and plan the upgrade. Severity is a starting point, not a verdict: a high-severity bug in a function you never call matters less than a medium one in your login code.

Indirect dependencies count too. If requests pulls in a vulnerable urllib3, that code runs in your app. Upgrading the package that depends on it is usually enough; the report says how for each package manager.

By file type

How to produce each lockfile, what to watch out for, and how to upgrade one package:

Checking a whole repository? The GitHub repo check finds every lockfile in a public repository.

Questions

Do you keep my lockfile?

No. We read the package names and exact versions from it and do not keep the file itself. The list of packages and your email address are kept for 90 days, for support and to stop abuse, then deleted. If you asked for product updates, only your address and that choice are kept after that.

Where does the vulnerability data come from?

From OSV.dev, the open vulnerability database. It brings together advisories from the GitHub Advisory Database, the Python Packaging Advisory Database, RustSec, the Go vulnerability database and others.

Why do I need the lockfile and not package.json or pyproject.toml?

package.json and pyproject.toml usually list version ranges, such as ^4.17.0. A vulnerability affects exact versions, so we need the file that records the versions you actually install: package-lock.json, yarn.lock, poetry.lock, uv.lock or a pinned requirements.txt.

A vulnerable package is not in my own dependencies. Why is it listed?

Lockfiles also list indirect (transitive) dependencies: the packages your packages depend on. They run in your app too. The report shows how to upgrade them: usually by upgrading the package that pulls them in.

How is this different from npm audit or pip-audit?

Those tools are great in a terminal. This check needs nothing installed, works the same way for Python, JavaScript, Go, Rust, Ruby and PHP lockfiles, groups advisories per package with the one upgrade that fixes them, and writes a prompt you can paste into your coding agent.

How often should I check?

New vulnerabilities are published every day, so a clean report is only true today. A free AIssue account checks your projects every day and emails you as soon as a new vulnerability affects one of them.

Last updated .