The author of this package has not provided a project description
Metadata
Release files for kinetix-contracts 1.0.12
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.12.tar.gz | 19.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kinetix_contracts-1.0.12-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 55.8 kB
Release files / kinetix_contracts-1.0.12.tar.gz
| Download URL | kinetix_contracts-1.0.12.tar.gz |
|---|---|
| Size | 19.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
94c05b765f904b10ca4ecc990ac5723077b34c110cd4c67da09029dcfb7e9949
|
|
BLAKE2b-256 checksum How to use checksums |
59f820d2d24b3bf9f84b42dbc928006e73c3381bd17e1388489c8f06bc8b4a8d
|
| 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.12-py3-none-any.whl
| Download URL | kinetix_contracts-1.0.12-py3-none-any.whl |
|---|---|
| Size | 36.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
abad0e817305669524144bc718b07d07ae3629a127bf64197d17971861153ddc
|
|
BLAKE2b-256 checksum How to use checksums |
57cd6d23e05f6394652eb4fd38a4b20e531f509ae88a6ad599b1c87ae2bbf717
|
| 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.12
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.