See the README on GitHub.
Metadata
Release files for django-blti 3.0.19
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 | |
|---|---|---|---|---|
| django_blti-3.0.19.tar.gz | 30.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_blti-3.0.19-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 72.8 kB
Release files / django_blti-3.0.19.tar.gz
| Download URL | django_blti-3.0.19.tar.gz |
|---|---|
| Size | 30.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e98bd438d1b7e724bfc8276d4585d26354f58252794edc8543524b25d281d78d
|
|
BLAKE2b-256 checksum How to use checksums |
8b760b1448a7ece92fb042ac6ec36a17927007d778c8b3a9c993f85b3e708908
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Release files / django_blti-3.0.19-py3-none-any.whl
| Download URL | django_blti-3.0.19-py3-none-any.whl |
|---|---|
| Size | 42.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a5094f2c72aabe3feefceac61f49982ec59da3c40182a5fc1c43116d357b1462
|
|
BLAKE2b-256 checksum How to use checksums |
a092a1eb0c9fb03510e8069472e3eb28d4ba2ca5ec9cc15ae6c04d0403b8f36a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Security for django-blti 3.0.19
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.