The author of this package has not provided a project description
Metadata
Release files for kinetix-contracts 1.4.1
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.4.1.tar.gz | 31.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kinetix_contracts-1.4.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 96.9 kB
Release files / kinetix_contracts-1.4.1.tar.gz
| Download URL | kinetix_contracts-1.4.1.tar.gz |
|---|---|
| Size | 31.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f9c4ba422c9f27ffb8edaf1aaa9a420b6099912378fd5063ab65bcd9afb7e57a
|
|
BLAKE2b-256 checksum How to use checksums |
702aa1ad0775746e1963f10a7dcff01186acfcd845f036746c3a871b828c9c48
|
| 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.4.1-py3-none-any.whl
| Download URL | kinetix_contracts-1.4.1-py3-none-any.whl |
|---|---|
| Size | 65.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fed900e072fb98336e4f932cfd624096e0ed0dba1dd64aca9b29241a376ec22f
|
|
BLAKE2b-256 checksum How to use checksums |
e23efb2427b720894a274646842d7a2dabe5ce42d25637de6cdc10ebf27a57c9
|
| 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.4.1
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.