The author of this package has not provided a project description
Metadata
Release files for cosmoner-sdk 1.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 | |
|---|---|---|---|---|
| cosmoner_sdk-1.4.0.tar.gz | 35.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cosmoner_sdk-1.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 60.9 kB
Release files / cosmoner_sdk-1.4.0.tar.gz
| Download URL | cosmoner_sdk-1.4.0.tar.gz |
|---|---|
| Size | 35.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4189530949c46ac6aa5636a02e8ed7c8d63113021bfe9485f79fe53a9c38c995
|
|
BLAKE2b-256 checksum How to use checksums |
edfe2e60b0d59d5275ec36e6feef7d25f194a44cd16b8abbc79dadcf7e1534d2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / cosmoner_sdk-1.4.0-py3-none-any.whl
| Download URL | cosmoner_sdk-1.4.0-py3-none-any.whl |
|---|---|
| Size | 25.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
921149bfd4546a17f34f2f1fb01fec360366376995a68783c0508fa5fde2608a
|
|
BLAKE2b-256 checksum How to use checksums |
450bab5efdb0e8d37e934256c826718eb7c5647b5c709879cca9a5a56cd7b9b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for cosmoner-sdk 1.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.