The author of this package has not provided a project description
Metadata
Release files for kinetix-contracts 1.0.14
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.14.tar.gz | 19.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kinetix_contracts-1.0.14-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 56.2 kB
Release files / kinetix_contracts-1.0.14.tar.gz
| Download URL | kinetix_contracts-1.0.14.tar.gz |
|---|---|
| Size | 19.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a15bfdc8de187ee944d6aed03bef417b9fae4ff324a213dd7537dae5b13ef4f2
|
|
BLAKE2b-256 checksum How to use checksums |
ef9b56a4facb5eee26f32eaeb76256bc1eeb0b7b1b89921c1d29581695ad6ef6
|
| 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.14-py3-none-any.whl
| Download URL | kinetix_contracts-1.0.14-py3-none-any.whl |
|---|---|
| Size | 37.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
05201dcf076c7f1088346fd779fb255cd193d56256708a5fc6971ccf340ffd22
|
|
BLAKE2b-256 checksum How to use checksums |
0eb9cddf9b44c01f3345a2c8824580b14312ac5a50e843c396188c5e61103e92
|
| 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.14
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.