The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for astrocoins 2.3.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.3.0.tar.gz | 3.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| astrocoins-2.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.6 kB
Release files / astrocoins-2.3.0.tar.gz
| Download URL | astrocoins-2.3.0.tar.gz |
|---|---|
| Size | 3.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
31798ccef20e0e57f80b0a9c5807d4ff2bcaa16506f4143c5914dc07a8e5ea99
|
|
BLAKE2b-256 checksum How to use checksums |
5fec5cd887a1ca64f7abb4e2d2e56aa191f105693d55411baaa5559e83ccee69
|
| 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.3.0-py3-none-any.whl
| Download URL | astrocoins-2.3.0-py3-none-any.whl |
|---|---|
| Size | 3.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1447034990f9fdf1201d58f7b5f9bcbdc812de141c93450947da48c90031afa8
|
|
BLAKE2b-256 checksum How to use checksums |
cd96d8a6d5110dfe04717cb0d7ca9dd81f64ee4b42ea2b8173bb6d4d9cb53d7b
|
| 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.3.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.
