Metadata
1 maintainer
Release files for Django-Persistent-Message 1.3.3
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_persistent_message-1.3.3.tar.gz | 29.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_persistent_message-1.3.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 62.6 kB
Release files / django_persistent_message-1.3.3.tar.gz
| Download URL | django_persistent_message-1.3.3.tar.gz |
|---|---|
| Size | 29.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9ff2815d5905b284e54ff0f42ec6112c03c94ad13a585f67848410315c4871d5
|
|
BLAKE2b-256 checksum How to use checksums |
0421ed51c9bd5c03c1ee35645d04af5063c1d409c40d0f85a017b27b46df7b31
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.11
|
Release files / django_persistent_message-1.3.3-py3-none-any.whl
| Download URL | django_persistent_message-1.3.3-py3-none-any.whl |
|---|---|
| Size | 33.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5f265212ce800f9d43e1ce8ef4195c5524b92626b3a1585a8a32ee9afc413fa4
|
|
BLAKE2b-256 checksum How to use checksums |
7c7ccee95bbbd3ffee218fd9716915763373fb6788256a20eab6b03546834271
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.11
|
Security for Django-Persistent-Message 1.3.3
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.
