The author of this package has not provided a project description
Metadata
Release files for kinetix-contracts 1.0.11
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.11.tar.gz | 18.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kinetix_contracts-1.0.11-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 55.4 kB
Release files / kinetix_contracts-1.0.11.tar.gz
| Download URL | kinetix_contracts-1.0.11.tar.gz |
|---|---|
| Size | 18.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d3c59f5e1568122674948ff81cb0caf8038cc65b2e675dfc791ab26613132d01
|
|
BLAKE2b-256 checksum How to use checksums |
e44d00d39fc05e7ce80520bd6b79ceed495c094370e95cd6fea76d5bf505ac7f
|
| 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.11-py3-none-any.whl
| Download URL | kinetix_contracts-1.0.11-py3-none-any.whl |
|---|---|
| Size | 36.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
af083cac14c762c33c60f27250c6749636782cd12e0962a4b63946912415c3af
|
|
BLAKE2b-256 checksum How to use checksums |
7816b35fee0519efd43a6d5c002b418e21a81d2c212944a691405c1f24c2aca6
|
| 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.11
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.