1 maintainer
Metadata
1 maintainer
Release files for django-multi-token 0.1.5
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-multi-token-0.1.5.tar.gz | 4.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_multi_token-0.1.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.4 kB
Release files / django-multi-token-0.1.5.tar.gz
| Download URL | django-multi-token-0.1.5.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
97b270cae1675d7c428a24f72dfb90fef8100898cce58c95450735c1306e7af0
|
|
BLAKE2b-256 checksum How to use checksums |
42d68e4e12bf1c483d577c59430fb64905aa58977977ba3648397e753de0abab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.7.3
|
Release files / django_multi_token-0.1.5-py3-none-any.whl
| Download URL | django_multi_token-0.1.5-py3-none-any.whl |
|---|---|
| Size | 5.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f7c7f8cb5a25c375c3a5ba291d8258d5a530dc3d17c82853054d18e2510326e3
|
|
BLAKE2b-256 checksum How to use checksums |
d3fda773e3c051e09f6652b39d15e84bb8bdcd899c2ec921d6fb4d8ba19604c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.7.3
|
Security for django-multi-token 0.1.5
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.
