The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for astrocoins 2.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 | Provenance | |
|---|---|---|---|---|
| astrocoins-2.5.0.tar.gz | 4.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| astrocoins-2.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.1 kB
Release files / astrocoins-2.5.0.tar.gz
| Download URL | astrocoins-2.5.0.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
efb7fb1f8ba127644bcf1f6e8b47073b0be2204772f1daf1c9c16cb2e28cd869
|
|
BLAKE2b-256 checksum How to use checksums |
3326a375070da46c6e844066b0501615ca0f4da83717163052a52b647fcc1d94
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / astrocoins-2.5.0-py3-none-any.whl
| Download URL | astrocoins-2.5.0-py3-none-any.whl |
|---|---|
| Size | 3.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c89f8001b6f5f26c74c5f98873da6e465c56a44bc6a40a6c3bf3379bee4a21d6
|
|
BLAKE2b-256 checksum How to use checksums |
c352b80f3422f9185e6da173194d8e4cab600927b59f26000c27cb9065989994
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for astrocoins 2.5.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.
