pypiage
A package for finding the least updated packages your project depends on.
Install
pip install pypiage
Usage
Quickly get the least updated packages referenced in your requirements.txt:
cat requirements.txt | pypiage
Find our when a certain python package was last updated:
echo django | pypiage
Output
You get a pipe | separated list of <package-name>|<upload-date>
where upload-date is the last recorded time the package was uploaded
to PyPi.
For example:
Given a requirements.txt like:
Flask==2.2.0
requests==2.28.0
numpy==1.24.2
When you give that file to pypiage:
pypiage requirements.txt
The output will list the latest uploaded date of the packages you gave pypiage:
INFO:pypiage:Getting package info for Flask
INFO:pypiage:Getting package info for requests
INFO:pypiage:Getting package info for numpy
requests|2023-01-12 16:24:54
numpy|2023-02-05 20:12:05
Flask|2023-02-15 22:43:57
Note:
If you don't like theINFOlog output, then you can turn logging off with:PYTHON_LOGLEVEL=ERROR pypiage requirements.txtto get less verbose output:
requests|2023-01-12 16:24:54
numpy|2023-02-05 20:12:05
Flask|2023-02-15 22:43:57
Remember you can also cat a list of packages to pypiage and it
will read from standard input:
cat requirements.txt | pypiage
Why does this exist?
I found myself with a large codebase and wanted to quicky get a sense of which package dependencies were likley no longer maintained (and therefore candidates for removal), and checking their last upload date is a reasonable first pass check.
Metadata
Release files for pypiage 0.1.5
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 |
|---|---|---|---|---|
| pypiage-0.1.5.tar.gz | 2.8 kB | Without provenance | Details for pypiage-0.1.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pypiage-0.1.5-py3-none-any.whl | Python 3 | none | any | Details for pypiage-0.1.5-py3-none-any.whl |
Total release size: 5.9 kB
Release files / pypiage-0.1.5.tar.gz
| Download URL | pypiage-0.1.5.tar.gz |
|---|---|
| Size | 2.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9f3c2ca229d96746e86f15fb684d5574f1766dcf2df5c3fb980cba6d9af1f193
|
|
BLAKE2b-256 checksum How to use checksums |
e1118525113bc2cd1a679e01ac4aadbb45ed3c3df1ba63a3215defb21c0c8646
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.6
|
Release files / pypiage-0.1.5-py3-none-any.whl
| Download URL | pypiage-0.1.5-py3-none-any.whl |
|---|---|
| Size | 3.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0ff78ffbc2f44ee83a046877a8220c74796f93c6bf9b8d660fdc707280eaf69d
|
|
BLAKE2b-256 checksum How to use checksums |
3d914d993002d953d3e1b2e2e67233c0ac3a9ca2eaae4bc3264e120cbb2f0893
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.6
|
Security for pypiage 0.1.5
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.