Metadata
Release files for django-aioredis 0.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_aioredis-0.0.1.tar.gz | 2.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_aioredis-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.2 kB
Release files / django_aioredis-0.0.1.tar.gz
| Download URL | django_aioredis-0.0.1.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
af8dd76d823711a61ae5053eda3c6bb2dce14aa7dd07133e70e1add099cfe46e
|
|
BLAKE2b-256 checksum How to use checksums |
856d18a7011f78e12e670fb1710d10ab5d1013a46e433f53d2baed139ed83b75
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.13.1
|
Release files / django_aioredis-0.0.1-py3-none-any.whl
| Download URL | django_aioredis-0.0.1-py3-none-any.whl |
|---|---|
| Size | 3.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d92a3c1e8d23a197a166a892e1318a4ca961283ace431b1d08db115d39b585ab
|
|
BLAKE2b-256 checksum How to use checksums |
a85db50eb972a15199890501db201d8369205854b47a25e9fc66c58a6baa6d20
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.13.1
|
Security for django-aioredis 0.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.