polarathene/teller — explained in plain English
Analysis updated 2026-07-18 · repo last pushed 2024-01-21
Run a process with secrets injected directly, avoiding .env files and shell history exposure
Preview available secrets safely using teller show with values masked
Scan a codebase for accidentally hardcoded secrets using teller scan
Redact sensitive values from logs by piping output through teller redact
| polarathene/teller | 0verflowme/alarm-clock | 0verflowme/seclists | |
|---|---|---|---|
| Language | — | CSS | — |
| Last pushed | 2024-01-21 | 2022-10-03 | 2020-05-03 |
| Maintenance | Dormant | Dormant | Dormant |
| Setup difficulty | moderate | easy | easy |
| Complexity | 3/5 | 2/5 | 1/5 |
| Audience | ops devops | vibe coder | ops devops |
Figures from each repo's GitHub metadata at analysis time.
Requires access to a supported secrets backend (Vault, AWS, GCP) and a .teller.yml config file.
A command-line secrets manager that pulls passwords and API keys from vaults like HashiCorp Vault or AWS Secrets Manager straight into your process, never your shell history.
Dormant — no commits in 2+ years (last push 2024-01-21).
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.