The author of this package has not provided a project description
Metadata
Release files for kinetix-contracts 0.1.21
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-0.1.21.tar.gz | 26.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kinetix_contracts-0.1.21-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 75.7 kB
Release files / kinetix_contracts-0.1.21.tar.gz
| Download URL | kinetix_contracts-0.1.21.tar.gz |
|---|---|
| Size | 26.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fb4c347239f34d5da26e0476fa269e2377ac162e246139608402a56410909c28
|
|
BLAKE2b-256 checksum How to use checksums |
dba466c9e421b9a4c039ffd6b5e2eac37b339b14e9b31d83b1aa62c93a54b2d7
|
| 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-0.1.21-py3-none-any.whl
| Download URL | kinetix_contracts-0.1.21-py3-none-any.whl |
|---|---|
| Size | 49.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
44f4a27075ce8f3f6f5d2b3764c1e92f6f319d7294f47884063d8f893550a49b
|
|
BLAKE2b-256 checksum How to use checksums |
78db0891cd15db67185f85f6b088a5a955e2cbc0e2943a3ab83f781b1b2ad4ed
|
| 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 0.1.21
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.