The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for latch-top 0.1.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 | |
|---|---|---|---|---|
| latch_top-0.1.0.tar.gz | 4.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| latch_top-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.9 kB
Release files / latch_top-0.1.0.tar.gz
| Download URL | latch_top-0.1.0.tar.gz |
|---|---|
| Size | 4.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8f81590cdaf903e3358e8a74dc0e3c77b0780d26ef8a5d765177ec5ac35322b3
|
|
BLAKE2b-256 checksum How to use checksums |
d636b862beeee93bdba97aecb8af1c89a77dd9553b712648bd61b6af99fa0de7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.6
|
Release files / latch_top-0.1.0-py3-none-any.whl
| Download URL | latch_top-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
44152298734173eeb0598a7662373b723f65fbc18ec57045f41fd5cf588b75d0
|
|
BLAKE2b-256 checksum How to use checksums |
35646d9a359cbe128d6011a12394a21b89024417f4d9369436a0e98c40096a17
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.6
|
Security for latch-top 0.1.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.
