pip-outdated
Find outdated dependencies in your requirements.txt or setup.cfg file. Report missing/outdated/incompatible packages with table and colors.
This tool compares the version number with the version specifier in requirements.txt or setup.cfg. If you just want to list all updatable package, simply use pip list --outdated command.
Installation
From pypi
pip install pip-outdated
Usage
usage: pip-outdated [-h] [-v] [-q] [<file> [<file> ...]]
Find outdated dependencies in your requirements.txt or setup.cfg file.
positional arguments:
<file> Read dependencies from requirements files. This option
accepts glob pattern. (default: ['requirements.txt',
'setup.cfg'])
optional arguments:
-h, --help show this help message and exit
-v, --verbose Print verbose information. (default: False)
-q, --quiet Don't return exit code 1 if not everything is up to date.
(default: False)
Check multiple files e.g. test-requirements.txt and dev-requirements.txt:
pip-outdated *-requirements.txt
Check files under requirements folder:
pip-outdated requirements/*.txt
Todos
Add options to update the package?
Add options to update the requirements.txt/setup.cfg file?
Add options to list all packages? (e.g. -g, --global)
Changelog
0.8.0 (Aug 9, 2025)
Change: drop setuptools dependency, switch to configparse for reading setup.cfg.
0.7.0 (Aug 13, 2024)
Change: ignore InvalidVersion error.
0.6.0 (Jan 1, 2023)
Bump dependencies.
Drop cchardet.
Change: fetch package version from pip CLI, so we can get package version in venv.
0.5.0 (Jan 12, 2022)
Bump dependencies.
Add: typehint.
0.4.0 (Jan 30, 2020)
Breaking: bump Python to 3.7
Add: request in parallel.
Add: --quiet option.
0.3.0 (Oct 13, 2019)
Breaking: set exit code to 1 if not all good.
Fix: don’t check prereleases.
Add: check setup_requires and extras_require in cfg files.
0.2.0 (Feb 10, 2019)
Bump dependencies:
0.1.0 (May 12, 2018)
First release.
Metadata
Release files for pip-outdated 0.8.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pip_outdated-0.8.0.tar.gz | 6.9 kB | Without provenance | Details for pip_outdated-0.8.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pip_outdated-0.8.0-py3-none-any.whl | Python 3 | none | any | Details for pip_outdated-0.8.0-py3-none-any.whl |
Total release size: 14.4 kB
Release files / pip_outdated-0.8.0.tar.gz
| Download URL | pip_outdated-0.8.0.tar.gz |
|---|---|
| Size | 6.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0a73f3261ee045e2fc682f4abe16043824c81eb2d667c76a13d687a581a66391
|
|
BLAKE2b-256 checksum How to use checksums |
beab839bc3128302e921a7ee395e2dcbba172c79dcd54ec9173e1f594db50449
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.5
|
Release files / pip_outdated-0.8.0-py3-none-any.whl
| Download URL | pip_outdated-0.8.0-py3-none-any.whl |
|---|---|
| Size | 7.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
383124bcde4dd3c8751a290044d3627934369608d5c34ff59b51ae1d10ad5a72
|
|
BLAKE2b-256 checksum How to use checksums |
1ae1851a1fc3a86e8ee030dfb3571aa6e18679fb1d681511c6728d5ed5287802
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.5
|
Security for pip-outdated 0.8.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.