The author of this package has not provided a project description
Metadata
Release files for kinetix-contracts 1.0.20
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 | |
|---|---|---|---|---|
| kinetix_contracts-1.0.20.tar.gz | 26.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kinetix_contracts-1.0.20-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 75.2 kB
Release files / kinetix_contracts-1.0.20.tar.gz
| Download URL | kinetix_contracts-1.0.20.tar.gz |
|---|---|
| Size | 26.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2ebb9680eb053fbc16322c5298bbcfb1de518d738b6e51aaf0ca1a3643400c9f
|
|
BLAKE2b-256 checksum How to use checksums |
daec5b8b058fac6fcda838370eb82b48b3c54f8874bf36339ad7f296395e1d8d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / kinetix_contracts-1.0.20-py3-none-any.whl
| Download URL | kinetix_contracts-1.0.20-py3-none-any.whl |
|---|---|
| Size | 49.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e5655d68cc25cdc66e21a1fd4faf2347405b9cc77be8558e91f9f3fb4fb3671d
|
|
BLAKE2b-256 checksum How to use checksums |
37c69f92d1ad52bf0ec18a7f08eeaa5a77127180c584c23e8b78cfcb409c0d3f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for kinetix-contracts 1.0.20
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.