Check Pipfile.lock for vulnerable dependencies

Upload or paste your Pipfile.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 Pipenv 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 Pipfile.lock

Pipfile.lock is written by Pipenv next to Pipfile. It is JSON, with the exact version and hashes of every package, in a "default" and a "develop" section.

To write or refresh it:

pipenv lock

Commit it with Pipfile; pipenv install --deploy refuses to install when they disagree.

Good to know

  • Pipfile alone cannot be checked: it has version ranges.
  • Both sections are checked: "default" (your app) and "develop" (development tools).

Fixing a vulnerable package

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

# Upgrade one package and update the lockfile
pipenv update package

For an indirect dependency, upgrade the package that depends on it, or add the fixed version to Pipfile and lock again.

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

pipenv check (or pip-audit on an exported requirements file) and this check

This check reads Pipfile.lock directly, with nothing to install, and groups advisories per package.

Other lockfiles

Last updated .