What the checker reads
A lockfile lists every package your project installs, at its exact version: the ones you chose and the hundreds they bring in. The checker reads those names and versions, then asks OSV.dev, the open advisory database run by Google, two questions about each: which advisories reach this exact version, and which exist for this package at all. OSV carries GitHub's reviewed advisories, the Python Packaging Authority's, and the OpenSSF list of malicious packages.
| What you give it | What it learns | How exact |
|---|---|---|
package-lock.json, pnpm-lock.yaml, yarn.lock, bun.lock | Every npm package installed, direct or brought in by another | Exact |
requirements.txt with pinned versions, poetry.lock, uv.lock | Every Python package installed | Exact |
package.json | Your direct dependencies, as ranges | The lowest version each range allows |
What happens to the file. It is sent to Keybrum once and read in memory for its package names and versions. Those names and versions are what OSV receives. Neither the file nor the list is stored or logged. If your lockfile names private packages you would rather not send, the Next.js and React CVE checker runs in your browser and sends nothing, for the four packages it covers.
How to read the result
- The verdict counts the advisories that reach your versions, and the upgrades that clear them. One upgrade often clears many: thirty advisories on an old
nextare one line of work. - Each upgrade names the package, the version you have and the version to take. That target is the lowest release that clears every advisory with a fix on your release line.
- A direct dependency is one your own
package.jsonnames: the checker gives the install command. A package brought in by another needs its parent upgraded, or an override. - Development only marks packages that never run in production, when the lockfile says so. They matter for your machine and your pipeline, less for your users.
- Used in attacks means the CVE is in CISA's Known Exploited Vulnerabilities catalog: someone was seen exploiting it. These go first.
- Malware is different from a vulnerability: that exact version was published to steal from whoever installs it. Remove it and rotate your secrets.
- Passed you by lists the advisories of the last 30 days for packages you use that do not reach your version. It is the part of the news you can skip.
Why the version to take is checked too
An advisory says which release fixes it. It does not say that release is clean. A fix for one flaw can land before the next advisory is published for the same package, and then the fixed version of the first sits inside the affected range of the second. The checker asks OSV about the target version itself and moves it up until nothing published reaches it. When it cannot, because an advisory has no fixed release yet, it says so instead of naming a version that would leave you exposed.
An advisory that reaches you is not always an exploit
The match is on versions, and it is exact. What a version cannot say is whether your app uses the affected code, or whether a stranger can reach it. The middleware bypass in Next.js (CVE-2025-29927) only matters if your app relies on middleware to keep a page closed. React2Shell (CVE-2025-55182) only matters if the app runs React Server Components. Upgrading is still the right move, since it costs less than being sure. For a few of them there is a faster answer: Keybrum sends the request the CVE needs to your live app and shows you whether it worked. The CVE watch pages say which.
Today's answer goes stale
Your lockfile does not change between two upgrades. The advisory database does, every day. A project that was clear on Monday can hold a critical flaw on Thursday without a single commit, because someone published what they found in a package you already had. Checking once tells you about the past.
Keybrum's CVE watch keeps the lockfile of each app and asks again every hour. When a new advisory reaches a version you run, you hear about it on Slack, Discord or email, with the upgrade already decided: the package, the version, the command. Your coding agent does the part that takes judgment, which is making the change and running your tests. Then Keybrum reads the versions your live app serves, and the advisory closes when the fixed one is there. The docs describe each step.
Questions
How do I check package-lock.json for vulnerabilities?
Drop the file on this page: you get every published advisory that reaches a version in it, and the release that fixes each. From a terminal, npm audit reads the same GitHub advisories for an npm project. This checker also reads pnpm, yarn, bun and Python lockfiles, checks the version it tells you to take, and marks what is used in attacks.
Does the checker keep my lockfile?
No. The file is read in memory for its package names and versions, and dropped. The names and versions are sent to OSV.dev to be matched. Nothing is stored or logged on Keybrum's side.
Is package.json enough?
It works, with less precision. "next": "^15.1.0" allows any later 15.x release, and only the lockfile records which one was installed. With a manifest, the checker evaluates the lowest version each range allows, and it does not see the packages your dependencies bring in, which is where most advisories land.
What does used in attacks mean?
The CVE is in the Known Exploited Vulnerabilities catalog kept by CISA, the US cybersecurity agency. An entry there means exploitation was observed, not only that it is possible. Most advisories never get there, so the ones that do deserve the first upgrade.
Does an advisory mean my app can be hacked?
It means a version you install has a published flaw. Whether a stranger can use it depends on your app: the feature has to be on and reachable. Upgrade anyway when a fix exists. For the CVEs it can prove, Keybrum attacks the live app and shows the result.
How often should I check my dependencies?
Advisories are published every day, so a check is out of date the next morning. Run it on every change to the lockfile at least. Keybrum's CVE watch asks again every hour for each app and tells you when a new advisory reaches a version you run.