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.
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
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 .