The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for astrocoins 2.2.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.2.0.tar.gz | 2.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| astrocoins-2.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.2 kB
Release files / astrocoins-2.2.0.tar.gz
| Download URL | astrocoins-2.2.0.tar.gz |
|---|---|
| Size | 2.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4c37e03166285f8815c091ce0d78398b1036ba01298049a6f4d8952d3e101a9c
|
|
BLAKE2b-256 checksum How to use checksums |
3ae41ce04e2dc719b02c18afd7e612fa763c6208e02e04c0b1b702f99a435b0c
|
| 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.2.0-py3-none-any.whl
| Download URL | astrocoins-2.2.0-py3-none-any.whl |
|---|---|
| Size | 3.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
40a9d94e00ece83d427ba9a8f06eef3a84293dbe400f400d5efa8d0c8bf1f1a0
|
|
BLAKE2b-256 checksum How to use checksums |
51fd7857bb0e8f11ee0195671768c93997f9ddafeab9e388a88b30cf2500789e
|
| 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.2.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.
