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