Metadata
Release files for tecton-utils 0.0.3
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 | |
|---|---|---|---|---|
| tecton_utils-0.0.3.tar.gz | 18.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tecton_utils-0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 35.6 kB
Release files / tecton_utils-0.0.3.tar.gz
| Download URL | tecton_utils-0.0.3.tar.gz |
|---|---|
| Size | 18.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
daeff7d8ef3715fc7e47bf68ee431d307558d6a6dd900c899e353bc8e3a8222b
|
|
BLAKE2b-256 checksum How to use checksums |
77bc4a5707551711731155b70eb7bf1a6de41c92bcebc074c52723d24d62b591
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.12.3
|
Release files / tecton_utils-0.0.3-py3-none-any.whl
| Download URL | tecton_utils-0.0.3-py3-none-any.whl |
|---|---|
| Size | 16.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d9aae5802473d67ddcb8a9230891c8ca5c6992c1f19253fe9b83f991b7f11617
|
|
BLAKE2b-256 checksum How to use checksums |
33430d8e506a9269db80f0c2a9197392574568ea3f961f9163a908fe49ef2ed9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.12.3
|
Security for tecton-utils 0.0.3
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.