The author of this package has not provided a project description
Metadata
Release files for kinetix-contracts 1.6.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 | |
|---|---|---|---|---|
| kinetix_contracts-1.6.0.tar.gz | 32.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kinetix_contracts-1.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 97.4 kB
Release files / kinetix_contracts-1.6.0.tar.gz
| Download URL | kinetix_contracts-1.6.0.tar.gz |
|---|---|
| Size | 32.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
68750417f5eaadac7282068de9729ef4d619f710438bbe08b1645a5305e310f0
|
|
BLAKE2b-256 checksum How to use checksums |
587ea341a10381ca363d5aac3072bdb519dd76e0caafa8645444dbd56b6f9209
|
| 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.6.0-py3-none-any.whl
| Download URL | kinetix_contracts-1.6.0-py3-none-any.whl |
|---|---|
| Size | 65.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
be5079274dbf10e6c79dbd1f2fadf3ad7c31ac1e6abc5c7ef7075dfb0bebff37
|
|
BLAKE2b-256 checksum How to use checksums |
f18429ef968396f4cf4582a2c4426862e77ac9dfd9ebe6080c94015bbada1512
|
| 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.6.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.