1 maintainer
Metadata
1 maintainer
Release files for wild-blue-yonder 0.0.6
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 | |
|---|---|---|---|---|
| wild_blue_yonder-0.0.6.tar.gz | 5.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| wild_blue_yonder-0.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.1 kB
Release files / wild_blue_yonder-0.0.6.tar.gz
| Download URL | wild_blue_yonder-0.0.6.tar.gz |
|---|---|
| Size | 5.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
893602e8cc9f12de755f720b1fa0577bb67e6075540fbc139080c29a561bedc8
|
|
BLAKE2b-256 checksum How to use checksums |
ba1f42e7f1a892013507410de272a8c540f8d040b978f33ceaab054b7858af54
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.9.21
|
Release files / wild_blue_yonder-0.0.6-py3-none-any.whl
| Download URL | wild_blue_yonder-0.0.6-py3-none-any.whl |
|---|---|
| Size | 7.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
08dab5606e9bc5c31f96c91b36a56ff2a76f63c7e166d7639f2659cefe623b4f
|
|
BLAKE2b-256 checksum How to use checksums |
ed7dc1d126cde18881ab9850c6569c4939b005bd5483b757ebad908d65af2ff8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.9.21
|
Security for wild-blue-yonder 0.0.6
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.
