The author of this package has not provided a project description
Metadata
Release files for kinetix-contracts 1.2.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.2.0.tar.gz | 29.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kinetix_contracts-1.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 86.1 kB
Release files / kinetix_contracts-1.2.0.tar.gz
| Download URL | kinetix_contracts-1.2.0.tar.gz |
|---|---|
| Size | 29.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f03963555a3732a9cf31ec5e787c9d58bdc8360e6e012f80400e435213750c7f
|
|
BLAKE2b-256 checksum How to use checksums |
ce7b4eabf6e1384dd74200151615850fefc2f2128fcc165f652ae77a7791c33c
|
| 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.2.0-py3-none-any.whl
| Download URL | kinetix_contracts-1.2.0-py3-none-any.whl |
|---|---|
| Size | 57.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e851078fe5af6874a47fd3f866423fbf9b154c7cc15477ee5a5e7728559755ba
|
|
BLAKE2b-256 checksum How to use checksums |
09bcbbab18728b66590784a4fd2e2ab631d6fd02076e51f81bc23ba93a26af44
|
| 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.2.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.