# Jwt implementation for Lever Microservices
Lever Application jwt package. You can use
Metadata
Release files for python-lever 0.2.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| python_lever-0.2.4-py3-none-any.whl | Python 3 | none | any | Details |
Release files / python_lever-0.2.4-py3-none-any.whl
| Download URL | python_lever-0.2.4-py3-none-any.whl |
|---|---|
| Size | 3.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5a310491fb988d69ebfc205c0c1d301688655931af7ad914a0128034909267a4
|
|
BLAKE2b-256 checksum How to use checksums |
5461874ba7e55e87c1da722f418405848e36309424e2742f148616e890a275de
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.6
|
Security for python-lever 0.2.4
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.