The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for astrocoins 2.1.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.1.0.tar.gz | 2.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| astrocoins-2.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.2 kB
Release files / astrocoins-2.1.0.tar.gz
| Download URL | astrocoins-2.1.0.tar.gz |
|---|---|
| Size | 2.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
216eb5fa58da61617e26d92f9c33bde2f48888720eacc9225da5b1323d53e2e3
|
|
BLAKE2b-256 checksum How to use checksums |
8fd51d1318cfa8120cc1ea483a869b51f2dfdac2216e3246272adca13332aa10
|
| 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.1.0-py3-none-any.whl
| Download URL | astrocoins-2.1.0-py3-none-any.whl |
|---|---|
| Size | 3.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6c2c8fe12e5f03e1178dee137b7bad34eee5658f35ebd6aaae693701c6b94641
|
|
BLAKE2b-256 checksum How to use checksums |
6fa4159f0b7673f74fd5a9055c1d4d32ebf9c7e54b39490b6cefc341f6f3097c
|
| 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.1.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.
