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