py-reess
CLI application for deterministic password generation and recall
Failing to REEcall your paSSword? Try py-REESS!
Install
pip install pyreess
Usage
pyreess --help
The core principle is simple - for the same input you get the same output. The input consists of input string, salt, length and alphabet (digits, lowercase, uppercase, symbols). Output is the generated password and can always be restored with the same input.
Metadata
Release files for pyreess 1.0
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 | Actions |
|---|---|---|---|---|
| pyreess-1.0.tar.gz | 3.3 kB | Without provenance | Details for pyreess-1.0.tar.gz |
Release files / pyreess-1.0.tar.gz
| Download URL | pyreess-1.0.tar.gz |
|---|---|
| Size | 3.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0918ed51af14673e47b927b0d325313d492f6a64c02b84e500540a36afb4382a
|
|
BLAKE2b-256 checksum How to use checksums |
ef32141445a74f853cb8427201180bd24a4e55fabd240801c3cfe7ad30f21324
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.48.2 CPython/3.7.7
|
Security for pyreess 1.0
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.