The author of this package has not provided a project description
Metadata
Release files for kinetix-contracts 1.0.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.0.0.tar.gz | 16.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kinetix_contracts-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 47.8 kB
Release files / kinetix_contracts-1.0.0.tar.gz
| Download URL | kinetix_contracts-1.0.0.tar.gz |
|---|---|
| Size | 16.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b4ac528fd0f128f16be7704ab41de9704edd90f5bf00661ce156d34b76233fa0
|
|
BLAKE2b-256 checksum How to use checksums |
65c6ee8dea71806c7b711054562adb059bf30f69e95579b847c60c151aa1a907
|
| 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.0-py3-none-any.whl
| Download URL | kinetix_contracts-1.0.0-py3-none-any.whl |
|---|---|
| Size | 30.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4b58ca0fbbd5a585385a8a8f44b974b3f6a0cff9bd854b6ab47c258f42d3cce3
|
|
BLAKE2b-256 checksum How to use checksums |
c85b8e832ffbf0362d7708ef3ccc4c7b2ac6461323dbedc366d75a6bd6b43e96
|
| 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.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.