Check pnpm-lock.yaml for vulnerable dependencies
Upload or paste your pnpm-lock.yaml. We check every JavaScript package version in it
against OSV.dev and email you the
vulnerable ones, the version that fixes them and the pnpm command to upgrade. Free, and no account needed.
About pnpm-lock.yaml
pnpm-lock.yaml is written by pnpm next to package.json (or at the root of a pnpm workspace). It records the exact version of every package, for every workspace project.
To write or refresh it:
pnpm install --lockfile-only
Commit it; pnpm install --frozen-lockfile fails in CI when it is out of date.
Good to know
- In a workspace there is one lockfile at the root for all projects: check that file.
- package.json cannot be checked: it has version ranges.
Fixing a vulnerable package
The report gives the fixed version for each vulnerable package (FIXED below). With pnpm:
# Upgrade one package
pnpm update package@FIXED
# In a workspace, in every project
pnpm update -r package@FIXED
For an indirect dependency, upgrade the parent, or force the version with "pnpm.overrides" in the root package.json, then run pnpm install.
Then run your tests and commit the updated pnpm-lock.yaml.
pnpm audit and this check
pnpm audit is built in. This check needs nothing installed and groups advisories per package with one target version.
Other lockfiles
Related free tools
GitHub repo vulnerability check
Paste a public GitHub repo URL. We find every lockfile, check each package version against OSV.dev and email you the fixes. Free, no account.
Dependency vulnerability check
Check requirements.txt, package-lock.json, poetry.lock and more against OSV.dev. Free report by email with fix commands. No account needed.
Last updated .