Metadata
Release files for django-oauth2 5.1.2
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_oauth2-5.1.2.tar.gz | 32.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_oauth2-5.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 76.4 kB
Release files / django_oauth2-5.1.2.tar.gz
| Download URL | django_oauth2-5.1.2.tar.gz |
|---|---|
| Size | 32.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
00908c800725b6331bd30f8f726934831c3a783078e1f5e579235730abd4776b
|
|
BLAKE2b-256 checksum How to use checksums |
78d65f2801032af3b118a302a7077b9b844b851d82cd666e269f45d5e8d7afdc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / django_oauth2-5.1.2-py3-none-any.whl
| Download URL | django_oauth2-5.1.2-py3-none-any.whl |
|---|---|
| Size | 43.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d4eec251031490f17c808a36968a94e867fe83a3cbf87f9d3efdda609283c411
|
|
BLAKE2b-256 checksum How to use checksums |
50d48f36c292649f40e2d5a84a6dd50bb0e8a5e331d7fe93840bca9ea0d86e3c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for django-oauth2 5.1.2
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.