The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for cosmoner-sdk 1.5.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.5.0.tar.gz | 39.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cosmoner_sdk-1.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 70.3 kB
Release files / cosmoner_sdk-1.5.0.tar.gz
| Download URL | cosmoner_sdk-1.5.0.tar.gz |
|---|---|
| Size | 39.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0e3bb337675d379360af43b49f806440ac418af5a72fac7ded30b8b443c7aad1
|
|
BLAKE2b-256 checksum How to use checksums |
12bae7b5be8367e7ba46f574967c3281e3b92d5d065c2d9d3bdc742e20a86472
|
| 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.5.0-py3-none-any.whl
| Download URL | cosmoner_sdk-1.5.0-py3-none-any.whl |
|---|---|
| Size | 30.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4842d84013288ef4369b8488800be1ed186660543bdb0187c8bfecb6c200effb
|
|
BLAKE2b-256 checksum How to use checksums |
ca3b5ac732674ff801fa3a1b921d77fdd6ea6a6245f4563663dd8f5988196534
|
| 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.5.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.
