Check uv.lock for vulnerable dependencies

Upload or paste your uv.lock. We check every Python package version in it against OSV.dev and email you the vulnerable ones, the version that fixes them and the uv command to upgrade. 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.

About uv.lock

uv.lock is written by uv next to pyproject.toml. Like poetry.lock, it records the exact version of every package uv resolved, for every platform the project supports.

To write or refresh it:

uv lock

uv sync also updates it. Commit it so CI and production install the same versions.

Good to know

  • The lockfile covers every platform and Python version the project supports, so it can list packages you never install on your own machine. They are checked too.
  • Workspace members share one uv.lock at the workspace root: check that file.

Fixing a vulnerable package

The report gives the fixed version for each vulnerable package (FIXED below). With uv:

# Upgrade one package in the lockfile
uv lock --upgrade-package package
# Install the new versions
uv sync

--upgrade-package works for indirect dependencies too, when the packages that depend on it allow the fixed version.

Then run your tests and commit the updated uv.lock.

pip-audit on uv export --format requirements-txt and this check

You can export a requirements file with uv export and check it with pip-audit. This check reads uv.lock directly.

Other lockfiles

Last updated .