The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for lbt-hub 0.0.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 | |
|---|---|---|---|---|
| lbt_hub-0.0.1.tar.gz | 372 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lbt_hub-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.3 kB
Release files / lbt_hub-0.0.1.tar.gz
| Download URL | lbt_hub-0.0.1.tar.gz |
|---|---|
| Size | 372 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7bb6caff1778bf0c9efd5426390e0b4e3193e83dce45c979006097f3bf49cbad
|
|
BLAKE2b-256 checksum How to use checksums |
e69639d40e43a30e1afe2717615f9a9e76581ee17ab6debfd7a0357c43eb0694
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Release files / lbt_hub-0.0.1-py3-none-any.whl
| Download URL | lbt_hub-0.0.1-py3-none-any.whl |
|---|---|
| Size | 938 Bytes |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
254119f3d26b051dcd8295f31594da9facda4089a67549e865777ba10f9aad22
|
|
BLAKE2b-256 checksum How to use checksums |
4432ef95c90b4455bfdaecf621086d20066e802125c547d43191d67468c174b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Security for lbt-hub 0.0.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.
