The author of this package has not provided a project description
Metadata
Release files for kinetix-contracts 1.3.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.3.0.tar.gz | 31.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kinetix_contracts-1.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 96.7 kB
Release files / kinetix_contracts-1.3.0.tar.gz
| Download URL | kinetix_contracts-1.3.0.tar.gz |
|---|---|
| Size | 31.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
66003ea0d23be239bb612d906d4acc86ab62d593a389f602f74322aa00f891ea
|
|
BLAKE2b-256 checksum How to use checksums |
7e77ed57a7489d89d9b5e86ca0e1a3c468ed416e98e81c7394415d8060f11592
|
| 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.3.0-py3-none-any.whl
| Download URL | kinetix_contracts-1.3.0-py3-none-any.whl |
|---|---|
| Size | 65.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
db0d1e65c5cde415f2983490086a5299329d7a2aad9b47864123c4aa7c83ec26
|
|
BLAKE2b-256 checksum How to use checksums |
d49fd264b16970491e9fd3f1cb0f3c823eba62fbf4745c42a284e3cd2662b420
|
| 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.3.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.