Our take
Quietno commits in the last 90 days and no release in a year- Activity
- 20
- Community
- 66
- Issues
- 21
- Pull requests
- 21
+0 stars in the last 8 days
Teller brings secret retrieval, command execution, scanning, and redaction into one Rust CLI, but its quiet recent activity and lack of a recent release warrant checking project maintenance against your adoption needs.
Good fit if
- Your developers already use Rust-compatible command-line tools and want secrets injected into local commands without keeping them in project files.
- You need a single workflow across supported secret providers, or want to use provider-held values for scanning and redaction.
- You are comfortable evaluating a project with no commits in the last 90 days and no release in over a year; contributor activity is not concentrated in one person.
Look elsewhere if
- Your team requires recent releases or visible recent issue handling before adopting a secrets tool. No issues were closed in the measured recent period.
- Your required secret provider or workflow is not supported by Teller's provider integrations.
- You need a tool whose development activity has been consistently recent.
All health signals
| Last commit | 2026-01-27 (8 months ago) |
|---|---|
| Commits, last 90 days | 0 |
| Releases, last 12 months | 0 (latest v2.0.7, 2024-05-20) |
| Contributors | 31 (top contributor: 42% of commits) |
| Issues closed, last 90 days | 0 |
| Project age | 5 years |
Checked on 2026-10-07 with the GitHub API.
Overview
Teller is a command-line tool for developers who need secrets from vaults, cloud services, or local dotenv files while developing and running applications. A YAML configuration maps keys from those sources, and Teller makes the resulting values available to commands without requiring developers to manage them through custom scripts or checked-in environment files.
Beyond loading secrets, Teller can scan code for values held in configured providers, redact secrets from text, and copy or write values between providers. It is most useful when a team wants one terminal workflow across multiple secret stores.
Key Features
- Load and map secrets from configured providers, including HashiCorp Vault, AWS Secrets Manager, Google Secret Manager, and dotenv files.
- Run a command with secrets supplied as environment variables.
- Populate the current shell or export secrets as JSON or YAML.
- Scan code for secrets and optionally fail a CI job when matches are found.
- Redact secrets from piped output, logs, and files.
- Copy, write, or delete values in providers that support those operations.
- Populate custom templates using secret values.
Use Cases
- Developers can run an application with staging or production-like environment values without storing those values in project files.
- Teams using multiple secret stores can configure a consistent CLI workflow instead of maintaining provider-specific scripts.
- CI maintainers can scan repositories for exposed secrets and make findings fail a build.
- Operators can redact known secrets from log streams or existing files before sharing or retaining them.
- Teams can copy or update values across configured providers when synchronizing environments.
What you need
Detected in the repository
- Rust (from Cargo.toml)
- Automated checks on GitHub Actions
License in plain words
Apache-2.0permissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license, the NOTICE file and a note of your changes
- Share your changes: no
- Includes an explicit patent grant from the contributors:
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
From the repository's teller-cli directory, install with Cargo:
cargo install --path .
Then create a configuration with teller new. See the repository README for provider setup and command details.
Considerations
The project is marked quiet: it has had no commits in the last 90 days, no release in over a year, and no issues closed in the measured recent period. Its contributor base is not concentrated in one person, but teams should still assess whether this maintenance pace is suitable for software that handles secrets. The README also marks the YAML export documentation as needing a rewrite, so verify that workflow before depending on it.
Found this useful?
Share it with someone who would like teller.