KEYS: Keeper, Exports Your Secrets
DISCLAIMER: This project is a private open source project and doesn't have any connection with Keeper Security.
A straightforward CLI wrapper for Keeper Commander that simplifies extracting secrets to setup environment variables.
keeper find-password does the same thing, except it doesn't handle SSO automatically and needs the --field parameter to work with API records.
Usage
# Set environment variable from a Keeper record
export OPENAI_API_KEY="$(keys 'OpenAI')"
# Specify a custom field
export SECRET="$(keys 'My secert record' --field 'password2')"
# Insert a new login secret
keys --insert OpenAI
# Insert a new login secret in a folder (however, the folder MUST exists)
keys --insert "Tools/OpenAI"
Installation
uv tool install .
Note: requires Keeper Commander to be installed and configured.
Default field by record type
The --field argument defaults to password for Login and Secure Note records and to API Key for API records.
SSO login
If SSO login is required, KEYS will automatically open the SSO login URL in your browser and wait till you paste the obtained login token in the terminal.
Donate
Donations via Liberapay or Bitcoin (1Ph3hFEoQaD4PK6MhL3kBNNh9FZFBfisEH) are always welcomed, thank you!
License
MIT
Metadata
Release files for keeper-keys 0.2.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 | |
|---|---|---|---|---|
| keeper_keys-0.2.0.tar.gz | 251.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| keeper_keys-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 257.1 kB
Release files / keeper_keys-0.2.0.tar.gz
| Download URL | keeper_keys-0.2.0.tar.gz |
|---|---|
| Size | 251.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d243f58222b78b3a45bb3d30138201cb6cf68c7bf277df51a53b5649c56ac46a
|
|
BLAKE2b-256 checksum How to use checksums |
3bb5365429149a80d6f30178372ca0a46311ed61ddb50563dc0f5dd3f8c3bf3c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 14, 2026.
Transparency logRelease files / keeper_keys-0.2.0-py3-none-any.whl
| Download URL | keeper_keys-0.2.0-py3-none-any.whl |
|---|---|
| Size | 5.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
29bb53a017855c36fae95b9ae637b300ba15a11f696fb4a1f811ac135033b5cb
|
|
BLAKE2b-256 checksum How to use checksums |
e96b281e5995588aced83007a6ac533da9fd940cf7f1aa67ace49d36f46674d3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 14, 2026.
Transparency logSecurity for keeper-keys 0.2.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for keeper_keys-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 14, 2026.
Transparency logA 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.