The author of this package has not provided a project description
Metadata
Release files for cosmoner-sdk 1.3.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.3.0.tar.gz | 33.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cosmoner_sdk-1.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 58.4 kB
Release files / cosmoner_sdk-1.3.0.tar.gz
| Download URL | cosmoner_sdk-1.3.0.tar.gz |
|---|---|
| Size | 33.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9784e2b8e5d79da888bce8757473341a140b36a7eee6014ba7d9e3232abe9515
|
|
BLAKE2b-256 checksum How to use checksums |
07bd14a50276b935ea23fd2cfd5a6a29d7cfba6378c1364cd2ffe24e0d02ce80
|
| 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.3.0-py3-none-any.whl
| Download URL | cosmoner_sdk-1.3.0-py3-none-any.whl |
|---|---|
| Size | 24.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f1e819b44901626975ebc502329572701cc7318bed443951e00a2a41c36d110b
|
|
BLAKE2b-256 checksum How to use checksums |
8910ce3f06bd7cb93d6b73d80c938f1b292e0fcd7dbe0f912fcbb627036a3ab7
|
| 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.3.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.