pypiratzzi
PyPI stopped accepting signatures for uploaded artifacts. pypiratzzi downloads all signatures for all releases for a project from PyPI.
One use-case for this is to commit all past signatures to source-control.
Using pypiratzzi
For example, I recently migrated “magic-wormhole” signatures from PyPI:
$ pypiratzzi --signatures ~/src/magic-wormhole/signatures magic-wormholeThis will use the PyPI Legacy API in JSON mode (as recommended by their documentation) to find all the releases and artifacts for “magic-wormhole”. It will then download any missing signatures; --signatures (defaults to .) says where to cache the signatures (and skips any already found locally).
1 maintainer
Metadata
1 maintainer
Release files for pypiratzzi 23.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 |
|---|---|---|---|---|
| pypiratzzi-23.8.0.tar.gz | 26.1 kB | Without provenance | Details for pypiratzzi-23.8.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pypiratzzi-23.8.0-py3-none-any.whl | Python 3 | none | any | Details for pypiratzzi-23.8.0-py3-none-any.whl |
Total release size: 41.4 kB
Release files / pypiratzzi-23.8.0.tar.gz
| Download URL | pypiratzzi-23.8.0.tar.gz |
|---|---|
| Size | 26.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4c7195350f7347ca52304d940250a86b43cc552d5ca116b0f06d7c73592eda9d
|
|
BLAKE2b-256 checksum How to use checksums |
fb7c3acf8d45f9d83cdbba216ab17900d7dbb9f724f45a5359719f315af0a844
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.1
|
Release files / pypiratzzi-23.8.0-py3-none-any.whl
| Download URL | pypiratzzi-23.8.0-py3-none-any.whl |
|---|---|
| Size | 15.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
812a41dfa78ac9a96733df8bf8ade64dc0eebec53fc16db400da37768e0bea90
|
|
BLAKE2b-256 checksum How to use checksums |
9019013075fd7b6f51092f0175b9f5c83e9f32fcb7b58c1b7a027ed781ee88b8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.1
|
Security for pypiratzzi 23.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.
