The author of this package has not provided a project description
Metadata
Release files for kinetix-contracts 1.0.15
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.15.tar.gz | 20.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kinetix_contracts-1.0.15-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 59.1 kB
Release files / kinetix_contracts-1.0.15.tar.gz
| Download URL | kinetix_contracts-1.0.15.tar.gz |
|---|---|
| Size | 20.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
059e443752589e9d80440071840532defaf12154bb17649861375fe97259a7ad
|
|
BLAKE2b-256 checksum How to use checksums |
d1903227f257370bcdf3a9b7e478956bb2cb70927d78732b66d8073fa3bbdfe4
|
| 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.15-py3-none-any.whl
| Download URL | kinetix_contracts-1.0.15-py3-none-any.whl |
|---|---|
| Size | 38.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d60eba8d0593ac268ca78d644f0629c44a71041d8df63b53d6b95def681eb7e9
|
|
BLAKE2b-256 checksum How to use checksums |
2786a8c5dcfea3464344b52900f24d79c2fc1c4693c9881ecf16fe578fbf76ec
|
| 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.15
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.