The author of this package has not provided a project description
Metadata
Release files for kinetix-contracts 1.0.17
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.17.tar.gz | 23.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kinetix_contracts-1.0.17-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 68.6 kB
Release files / kinetix_contracts-1.0.17.tar.gz
| Download URL | kinetix_contracts-1.0.17.tar.gz |
|---|---|
| Size | 23.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e27f24babfa0221ca4154eeb8ab4adafcfb7c4b89bad3fab8d140e1053ee828b
|
|
BLAKE2b-256 checksum How to use checksums |
0106f89768df6e1afbcf07593e51b5a469c52023a1a4f2191d0eb65e752d1f3b
|
| 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.17-py3-none-any.whl
| Download URL | kinetix_contracts-1.0.17-py3-none-any.whl |
|---|---|
| Size | 44.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
040b84d431a542a18da8a97661ecebb173ab921b6d27287598e049f35342d6af
|
|
BLAKE2b-256 checksum How to use checksums |
958df57f89bd1f7628dc89875df59ca4abf7c4ced288bc12ee942a9decae971b
|
| 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.17
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.