See the README on GitHub.
2 maintainers
Metadata
2 maintainers
Release files for Django-UserService 3.2.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_userservice-3.2.2.tar.gz | 12.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_userservice-3.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.3 kB
Release files / django_userservice-3.2.2.tar.gz
| Download URL | django_userservice-3.2.2.tar.gz |
|---|---|
| Size | 12.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6b4335166affe38a34f79613273f18d9b3122aa0f879118938f3c0327e264e2d
|
|
BLAKE2b-256 checksum How to use checksums |
4769d5632c176ae4d324c391de2c5edb86a370c6a6567133ae24403b43cf9d26
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.10
|
Release files / django_userservice-3.2.2-py3-none-any.whl
| Download URL | django_userservice-3.2.2-py3-none-any.whl |
|---|---|
| Size | 16.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
27d2ff56a3aa21d24029cda011d00d89bceca0a438bdf3872b672a69c86a757d
|
|
BLAKE2b-256 checksum How to use checksums |
73b401756ec68a5d932cf4db909a3c64277e17aa9d4beffa9ab4c28582bb5f19
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.10
|
Security for Django-UserService 3.2.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.
