The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for astrocoins 2.6.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.6.0.tar.gz | 4.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| astrocoins-2.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.0 kB
Release files / astrocoins-2.6.0.tar.gz
| Download URL | astrocoins-2.6.0.tar.gz |
|---|---|
| Size | 4.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5f9ba2ccac74a8ea3a6fda19d26fa28cc0732782f664929e5f8184505bab0709
|
|
BLAKE2b-256 checksum How to use checksums |
c1c9b58d7b8f722b4d9e1d67a2bf8c14e37496fa12f73dc964c88d14c159b695
|
| 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.6.0-py3-none-any.whl
| Download URL | astrocoins-2.6.0-py3-none-any.whl |
|---|---|
| Size | 3.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4c1b03b06c87dd8116619f69792016ba40c8f6027ce9393d0bc7634af23e1688
|
|
BLAKE2b-256 checksum How to use checksums |
47944a30d12a7d995f1ea698fd47975a4172dc26428df1c866f831967d256885
|
| 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.6.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.
