Metadata
Release files for django-imagedeck 0.4.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 | |
|---|---|---|---|---|
| django_imagedeck-0.4.0.tar.gz | 34.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_imagedeck-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 79.6 kB
Release files / django_imagedeck-0.4.0.tar.gz
| Download URL | django_imagedeck-0.4.0.tar.gz |
|---|---|
| Size | 34.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
58d6c5fc2a1311ecc50f18bd3cfbf4f6a2d8f2098e80829c92164f90999aa9fe
|
|
BLAKE2b-256 checksum How to use checksums |
f6d881300677190682f44c44347d5403323d10c7b6fa6b270171180a7aea89b8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.0.1 CPython/3.13.1 Darwin/24.3.0
|
Release files / django_imagedeck-0.4.0-py3-none-any.whl
| Download URL | django_imagedeck-0.4.0-py3-none-any.whl |
|---|---|
| Size | 44.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
415ab8a8dbf07886785ab2a8a5b9e5c56ea082583ef10039e711970c1f22f51c
|
|
BLAKE2b-256 checksum How to use checksums |
8c99527019240ad2ff71092c07029cfcf70bd718b179aee5c9b7b2555d05f308
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.0.1 CPython/3.13.1 Darwin/24.3.0
|
Security for django-imagedeck 0.4.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.