The author of this package has not provided a project description
6 maintainers
Metadata
6 maintainers
Release files for django-agnocomplete 0.11.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-agnocomplete-0.11.0.tar.gz | 33.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_agnocomplete-0.11.0-py2-none-any.whl | Python 2 | none | any | Details |
Total release size: 50.5 kB
Release files / django-agnocomplete-0.11.0.tar.gz
| Download URL | django-agnocomplete-0.11.0.tar.gz |
|---|---|
| Size | 33.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4d11dd1674c2011b0607c5d0819af5d65bbc5ee33b239351c3542967fa795345
|
|
BLAKE2b-256 checksum How to use checksums |
234e3ecaf338ff927c2725a8ba2d6056493fa0065387227d8e6f2a2d9fb4edfe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / django_agnocomplete-0.11.0-py2-none-any.whl
| Download URL | django_agnocomplete-0.11.0-py2-none-any.whl |
|---|---|
| Size | 16.7 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
80d63329dbcd61b5ac8b60d2d5c4f3fb833bec6a1ed2d3ba652a2440f787ac12
|
|
BLAKE2b-256 checksum How to use checksums |
11992ad6ff0c80556ec76aa2d67c1d7f76258522be8c7d4e8858d5a1e42a476f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-agnocomplete 0.11.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.
