The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for astrocoins 2.4.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.4.0.tar.gz | 4.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| astrocoins-2.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.0 kB
Release files / astrocoins-2.4.0.tar.gz
| Download URL | astrocoins-2.4.0.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
193944f9cbf60e153b7abd7a13bb8a3ead3512bd709f89aa07a38f3328030ad5
|
|
BLAKE2b-256 checksum How to use checksums |
4b90685365d01acda4db4ebf12e1f9b103fbf9839fccd492a5739f4f470003d2
|
| 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.4.0-py3-none-any.whl
| Download URL | astrocoins-2.4.0-py3-none-any.whl |
|---|---|
| Size | 3.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3f34354a002fb546ca327eef68df81567741d75eb3848fe535a1b56fd78c1e39
|
|
BLAKE2b-256 checksum How to use checksums |
aae183155c7ae5bc89277943eb442549afe5ec5346431054dcbc75ccdac5af30
|
| 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.4.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.
