1 maintainer
Metadata
1 maintainer
Release files for django-lispy-filter 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_lispy_filter-0.1.5.tar.gz | 4.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_lispy_filter-0.1.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.5 kB
Release files / django_lispy_filter-0.1.5.tar.gz
| Download URL | django_lispy_filter-0.1.5.tar.gz |
|---|---|
| Size | 4.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4d3600db3f3ea6c690aca81396401a60586b4e99f851b77d0fbd56ea189585fd
|
|
BLAKE2b-256 checksum How to use checksums |
806370bffce5cc3c8f31565bea8988404d7e3c3618255270ae429c17c0bb8e7b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Release files / django_lispy_filter-0.1.5-py3-none-any.whl
| Download URL | django_lispy_filter-0.1.5-py3-none-any.whl |
|---|---|
| Size | 5.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
becdb8dc63c5d8fa21aac5204e9a41b54425e1e32290698d0070c3c4b6459705
|
|
BLAKE2b-256 checksum How to use checksums |
8d9e47deb48459173a1ebeadd0cb66d9045229acfc5162e5300c2054e7d63fb8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Security for django-lispy-filter 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.
