A single sign on(sso) system drive by python
install
python3 -m pip install husky
require
PySSO based on python3, and those libs was required.
Tornado
if you use pip install PySSO, the requirements will be install automatic.
Desc
ToDo:…
You can see detail documents over https://github.com/alexazhou/PySSO
Metadata
Release files for PySSO 0.0.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 | |
|---|---|---|---|---|
| PySSO-0.0.2.tar.gz | 5.6 kB | Without provenance | Details |
Release files / PySSO-0.0.2.tar.gz
| Download URL | PySSO-0.0.2.tar.gz |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6291d50fdd34e592b50a39628bd77a4045b78b4942b82863b75ee40ddf553947
|
|
BLAKE2b-256 checksum How to use checksums |
d5cd6c8f40e6527ae9c2c2f061fa025049427a4cf7b680e108614b657c2be97f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for PySSO 0.0.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.