The author of this package has not provided a project description
Metadata
Release files for cosmoner-sdk 1.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 | |
|---|---|---|---|---|
| cosmoner_sdk-1.2.0.tar.gz | 29.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cosmoner_sdk-1.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 51.7 kB
Release files / cosmoner_sdk-1.2.0.tar.gz
| Download URL | cosmoner_sdk-1.2.0.tar.gz |
|---|---|
| Size | 29.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
31a908fd92da69d6f9a72f1faac0734634dc244805992972cb4752a6ae04acb7
|
|
BLAKE2b-256 checksum How to use checksums |
51e154d8b58f6cbb44b862d020b6ea6787133122394b0b5c063cc86177664427
|
| 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.2.0-py3-none-any.whl
| Download URL | cosmoner_sdk-1.2.0-py3-none-any.whl |
|---|---|
| Size | 22.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e47f3a5148fab1744814d6eb0283511ef27690cdb3249b4c2939e6010e6a326e
|
|
BLAKE2b-256 checksum How to use checksums |
decd97f40e6438adae09148f840eea469cb0f5f11cff5b29bbdb4bab57778cbf
|
| 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.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.