The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for astrocoins 2.0.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.0.0.tar.gz | 2.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| astrocoins-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.5 kB
Release files / astrocoins-2.0.0.tar.gz
| Download URL | astrocoins-2.0.0.tar.gz |
|---|---|
| Size | 2.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9a5d3ad600782cef7bbe51506b4dac7b343bab7700e9498175a4ab958c12f909
|
|
BLAKE2b-256 checksum How to use checksums |
dad458aa41e005abcc469773586e80d4747342aa4e5464f65dcefdd60a3db7aa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Release files / astrocoins-2.0.0-py3-none-any.whl
| Download URL | astrocoins-2.0.0-py3-none-any.whl |
|---|---|
| Size | 3.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9d6d2cff0d34d6fa02415bea318a74080baaa4382068dc0bf543d4e8c262d35a
|
|
BLAKE2b-256 checksum How to use checksums |
5e35a84784deb031e24100cf0f9e4ed26e30d130c5fd1c39407d92dbe9d3d980
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Security for astrocoins 2.0.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.
