Metadata
1 maintainer
Release files for Uw-Django-Oidc 1.0.2.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 | |
|---|---|---|---|---|
| uw_django_oidc-1.0.2.1.tar.gz | 12.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| uw_django_oidc-1.0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 28.1 kB
Release files / uw_django_oidc-1.0.2.1.tar.gz
| Download URL | uw_django_oidc-1.0.2.1.tar.gz |
|---|---|
| Size | 12.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b3af285c5db19e466987745324b3e60b761c942c190bce29510b39d6e04166a7
|
|
BLAKE2b-256 checksum How to use checksums |
6344f632db1aa551d0c9c5c14d4e0c9e9e5cb21f9eae0a204babb45e06432407
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.13
|
Release files / uw_django_oidc-1.0.2.1-py3-none-any.whl
| Download URL | uw_django_oidc-1.0.2.1-py3-none-any.whl |
|---|---|
| Size | 15.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9694ea1ae750df5b30210c8eb3c09754df26b39eab7d5167f50038cc521e19ca
|
|
BLAKE2b-256 checksum How to use checksums |
c3ec639b0fb08475cf894d84618d2a807f4943b38f7271cafa17382bdacc57f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.13
|
Security for Uw-Django-Oidc 1.0.2.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.
