Metadata
Release files for django-commons-playground 1.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 | |
|---|---|---|---|---|
| django_commons_playground-1.0.1.tar.gz | 2.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_commons_playground-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.2 kB
Release files / django_commons_playground-1.0.1.tar.gz
| Download URL | django_commons_playground-1.0.1.tar.gz |
|---|---|
| Size | 2.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d091d6d1a1c3669433ba714eaebe410a4ff08d00bc8afd05daee65c8226b5a9c
|
|
BLAKE2b-256 checksum How to use checksums |
da65f659242d6400ee342a418e346209a351c4c2bb9675926609688214476ad9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.4
|
Release files / django_commons_playground-1.0.1-py3-none-any.whl
| Download URL | django_commons_playground-1.0.1-py3-none-any.whl |
|---|---|
| Size | 2.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d495683b816dda90fccd05d9a5cac70e2415b3c83dda3c0f6b2cc9a030ab9ab0
|
|
BLAKE2b-256 checksum How to use checksums |
b1817f0db6a78915a69a5a8631940b336d1aec0f90b61f8a3611cedc07ba49ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.4
|
Security for django-commons-playground 1.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.