The author of this package has not provided a project description
Metadata
Release files for kinetix-contracts 1.0.21
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.21.tar.gz | 26.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kinetix_contracts-1.0.21-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 75.7 kB
Release files / kinetix_contracts-1.0.21.tar.gz
| Download URL | kinetix_contracts-1.0.21.tar.gz |
|---|---|
| Size | 26.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e4d4e154e3e15292eb401e75e5ed2452953b275618b8c5d36126d7d1c07ef0fa
|
|
BLAKE2b-256 checksum How to use checksums |
99743cf6d3439a10ef3c52a0929e06756fa78083cb53c974589c1e7c50b10b3f
|
| 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.21-py3-none-any.whl
| Download URL | kinetix_contracts-1.0.21-py3-none-any.whl |
|---|---|
| Size | 49.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8d0a2cf5ea253177c3578dee4b39d7aa457c3e75869554d10a6914a86a7f2a7e
|
|
BLAKE2b-256 checksum How to use checksums |
a402d33c400630dc5415037bd9777d3ad27104344b6d20a991e1e61f991b64cf
|
| 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.21
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.