The author of this package has not provided a project description
Metadata
Release files for kinetix-contracts 1.0.19
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.19.tar.gz | 26.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kinetix_contracts-1.0.19-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 74.8 kB
Release files / kinetix_contracts-1.0.19.tar.gz
| Download URL | kinetix_contracts-1.0.19.tar.gz |
|---|---|
| Size | 26.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
29ea4cfa25d442d6af76cacca74d7bd193c040f35c9d198514271800dea5eb5c
|
|
BLAKE2b-256 checksum How to use checksums |
8c5889a2113f8b40aa765ac4bb6c83652eaa7546646e0219b882f063eb6eae01
|
| 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.19-py3-none-any.whl
| Download URL | kinetix_contracts-1.0.19-py3-none-any.whl |
|---|---|
| Size | 48.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a645a8f68b53153558a52886c7d294be3aa6e04ef5396967451a208c1065c8bc
|
|
BLAKE2b-256 checksum How to use checksums |
7181c01093e29a636a30afe05f8a8cc8343249671bfcd68fdf236fb15e84c66c
|
| 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.19
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.