1 maintainer
Metadata
1 maintainer
Release files for get-cosmopower-emus 0.0.16
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 | |
|---|---|---|---|---|
| get_cosmopower_emus-0.0.16.tar.gz | 2.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| get_cosmopower_emus-0.0.16-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.1 kB
Release files / get_cosmopower_emus-0.0.16.tar.gz
| Download URL | get_cosmopower_emus-0.0.16.tar.gz |
|---|---|
| Size | 2.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d211abb2b6ff4188b518f4c8450d87842b1176ef6c8dfa430bd5d33399fdff7c
|
|
BLAKE2b-256 checksum How to use checksums |
2959f6d5d8d0b99797af16c0e9cb196f45a81812e35024b800de4b4168af53ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.9.21
|
Release files / get_cosmopower_emus-0.0.16-py3-none-any.whl
| Download URL | get_cosmopower_emus-0.0.16-py3-none-any.whl |
|---|---|
| Size | 2.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2fc64af059796c5e7b8a2593ae6f93458baa2a58e2160b7d37ca51fcb08e20f1
|
|
BLAKE2b-256 checksum How to use checksums |
33305030410ce336980df8d5cd10e37021135b7a5908b0ece97092af563c54aa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.9.21
|
Security for get-cosmopower-emus 0.0.16
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.
