1 maintainer
Metadata
1 maintainer
Release files for polyquack-django 0.2
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 | |
|---|---|---|---|---|
| polyquack-django-0.2.tar.gz | 2.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| polyquack_django-0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.5 kB
Release files / polyquack-django-0.2.tar.gz
| Download URL | polyquack-django-0.2.tar.gz |
|---|---|
| Size | 2.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ef382864a457be988f4782f21f272ee18b57cd6b90762fe0c1f4e2e06e19d51e
|
|
BLAKE2b-256 checksum How to use checksums |
ee83d1a23196fa6e366628683b071285bb708fccae240d3a1cba39ed8300b78e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.10 CPython/3.8.5 Linux/5.8.3-arch1-1
|
Release files / polyquack_django-0.2-py3-none-any.whl
| Download URL | polyquack_django-0.2-py3-none-any.whl |
|---|---|
| Size | 3.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d25878d852337103dba8d92c7813d4f871646d6f8fdbf124a2bb96cbea98ef97
|
|
BLAKE2b-256 checksum How to use checksums |
22b8878e85afaa64e971428bea1827c863de496b45a83bc145ae5dc3b85ee644
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.10 CPython/3.8.5 Linux/5.8.3-arch1-1
|
Security for polyquack-django 0.2
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.
