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