1 maintainer
Metadata
1 maintainer
Release files for django-sage-session 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_sage_session-0.1.5.tar.gz | 15.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_sage_session-0.1.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 36.8 kB
Release files / django_sage_session-0.1.5.tar.gz
| Download URL | django_sage_session-0.1.5.tar.gz |
|---|---|
| Size | 15.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5025f146a03bbddf6531f75d3b0272334df9ec2125b7b4404d62f3bff27ea1b2
|
|
BLAKE2b-256 checksum How to use checksums |
c155575e5ea450309af6e3dd2aaf68350a18b4688960363f5fe3636c2067a0cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.3 CPython/3.12.4 Windows/11
|
Release files / django_sage_session-0.1.5-py3-none-any.whl
| Download URL | django_sage_session-0.1.5-py3-none-any.whl |
|---|---|
| Size | 21.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1752c22788aaeeb422eec4aab6ef0f1cec9be0cd0bb1a8b85949fda85b5d782d
|
|
BLAKE2b-256 checksum How to use checksums |
ac1bf2fab66e2bf1c867777f7c965123ec5dce2a41edebc96353e48073d85525
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.3 CPython/3.12.4 Windows/11
|
Security for django-sage-session 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.
