The author of this package has not provided a project description
Metadata
Release files for blt-trainer 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 | |
|---|---|---|---|---|
| blt_trainer-0.1.0.tar.gz | 8.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| blt_trainer-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 19.2 kB
Release files / blt_trainer-0.1.0.tar.gz
| Download URL | blt_trainer-0.1.0.tar.gz |
|---|---|
| Size | 8.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4f4277fc3d8ec4e732029f51dab48b7dbd749eb363ec397cd43a1ce80653cd03
|
|
BLAKE2b-256 checksum How to use checksums |
597675953a43325971bfe002e1ffe673b30fec138c283163d8c55f5b278859e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Release files / blt_trainer-0.1.0-py3-none-any.whl
| Download URL | blt_trainer-0.1.0-py3-none-any.whl |
|---|---|
| Size | 10.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c447765ff6fbb2b4e2f6e67b7986758bc2e9bbbd7220f2aba82f1929cfd62bab
|
|
BLAKE2b-256 checksum How to use checksums |
4d4a350212ef4d6cb257d350250397c9d524b53616e32e3bee68ae93f0beb14f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for blt-trainer 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.