pip-abandoned
Installation
I recommend installing pip-abandoned with pipx. This will give you a system-wide install of pip-abandoned with its dependencies isolated from any environments you intend to scan.
Alternatively pip-abandoned can be installed from PyPI with your package manager of choice: pip, poetry, pipenv, etc.
Introduction
Some package registries like NPM and Packagist allow a user to mark a package as abandoned or deprecated. This means it is relatively easy to tell if you are relying on a package abandoned by its author. It also allows package managers to consume this metadata to provide a warning at install time. PyPI does not have a mechanism to abandon or deprecate a package. There are some signals we can look at though.
- Many packages are linked to a GitHub repository. If that GitHub repository is archived, this is a strong signal that the package itself is abandoned
- Some packages may use the
Development Status :: 7 - Inactivetrove classifier to indicate the package is not actively maintained - Some packages may include a
badge in the project README to indicate the package is not actively maintained
pip-abandoned uses these signals to identify potentially abandoned packages in your environment.
Authentication
pip-abandoned uses the GitHub GraphQL API to efficiently query many repos at once. The advantage of this is that it is fast. The tradeoff is that authentication is required. A PAT with read-only access to public repos will be sufficient for most cases. There are two ways we can provide an auth token:
- Via an environment variable called
GH_TOKENe.g:GH_TOKEN=ghp_abc123 - Run
pip-abandoned set-tokento store a token using the system keyring service with keyring
Usage
# Search a virtualenv path:
pip-abandoned search /home/alice/.virtualenvs/myproject/lib/python3.10/site-packages
# Search a requirements file:
pip-abandoned search -r /path/to/requirements.txt
When searching one or more requirements files, your packages will be installed into a temporary virtualenv. This means this search will include transitive dependencies.
Exit Codes
pip-abandoned search exits with
- code
0when no inactive, archived or unmaintained packages were found - code
1when an error was encountered. For example:- no packages were supplied in the path provided or
- no auth token was supplied
- code
9when one or more inactive, archived or unmaintained packages were found
Inspiration
pip-abandoned takes inspiration from pip-audit, another great project.
Release files for pip-abandoned 0.5.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 | |
|---|---|---|---|
| pip_abandoned-0.5.0.tar.gz | 13.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pip_abandoned-0.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.9 kB
Release files / pip_abandoned-0.5.0.tar.gz
| Download URL | pip_abandoned-0.5.0.tar.gz |
|---|---|
| Size | 13.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
989d100b383829f90138fab2f2ca6d58a0b439472ff4ec85ee5bc7062b575328
|
|
BLAKE2b-256 checksum How to use checksums |
55e2f6cf13ef1b83045b2b076249c63dd23ccbc0148264d8546946f46ac4bc79
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 25, 2025.
Transparency logRelease files / pip_abandoned-0.5.0-py3-none-any.whl
| Download URL | pip_abandoned-0.5.0-py3-none-any.whl |
|---|---|
| Size | 8.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2aa2300edbf37253bd8effce976a28c001953b674c2d99da3148da169dbffb5a
|
|
BLAKE2b-256 checksum How to use checksums |
cc35e5e40dca12bed4ce2e645817c4c63338e038fe6954983d2c20114db93c40
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 25, 2025.
Transparency log