The author of this package has not provided a project description
Metadata
Release files for kinetix-contracts 1.0.16
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.16.tar.gz | 22.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kinetix_contracts-1.0.16-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 64.4 kB
Release files / kinetix_contracts-1.0.16.tar.gz
| Download URL | kinetix_contracts-1.0.16.tar.gz |
|---|---|
| Size | 22.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5dc3f6d352a253480e49fcc62f94a1d43fee30e790ec1b63b5e74f30d0da6f53
|
|
BLAKE2b-256 checksum How to use checksums |
0872b104084d893ce4b1fc809aae8e164c3369bfcafa8e51c1ed69259400a3c4
|
| 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.16-py3-none-any.whl
| Download URL | kinetix_contracts-1.0.16-py3-none-any.whl |
|---|---|
| Size | 42.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
36a0dba5fb6fd86413c38dbaeb80b426cb1869c4f4a172f8450f49a3859b64f5
|
|
BLAKE2b-256 checksum How to use checksums |
8e68a5134e10a40b20cf78c88833064947a9c4da893b6c716e2eda61a5b76c8d
|
| 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.16
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.