This is a placeholder package to reserve the llm-deep-bloom name on PyPI.
Metadata
Release files for llm-deep-bloom 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 | |
|---|---|---|---|---|
| llm_deep_bloom-0.0.1.tar.gz | 1.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| llm_deep_bloom-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.8 kB
Release files / llm_deep_bloom-0.0.1.tar.gz
| Download URL | llm_deep_bloom-0.0.1.tar.gz |
|---|---|
| Size | 1.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b21f6f222542296f26b2791dc9b0c9a8c9cf8ad057fab70eea774636447e0af2
|
|
BLAKE2b-256 checksum How to use checksums |
9db982c190c0f71cf2d959ea2db90e0a65885001892f3e6996380b312f1e4cc3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.1
|
Release files / llm_deep_bloom-0.0.1-py3-none-any.whl
| Download URL | llm_deep_bloom-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2f6db3152b94e8f5441403287e2f977bb68483487d8e74ca672a900e8b195a34
|
|
BLAKE2b-256 checksum How to use checksums |
2998010e4ac05efacad12d8fd9959bd40d4d3f77c954090079f51d798267bed1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.1
|
Security for llm-deep-bloom 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.