tellerops/teller

Cloud native secrets management for developers - never leave your command line for secrets.

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 21st, 2026
Created on March 24th, 2021
Open Issues & Pull Requests: 52 (+0)
GitHub issues: Enabled
Number of forks: 201
Total Stargazers: 3,231 (+0)
Total Subscribers: 29 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.6 days
Mean response time: 75.9 days
90th percentile: 254.9 days
Tracked items: 15

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 19
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 690 days
Stale 30+ days: 19
Stale 90+ days: 17

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (3)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Teller is a command-line secrets management tool that integrates with multiple secret backends to provide unified access to credentials without switching contexts.

The tool solves the friction of managing secrets across different platforms and services. Developers working with cloud infrastructure often need to access credentials stored in various backends—AWS Secrets Manager, HashiCorp Vault, and others—but switching between tools and interfaces breaks workflow. Teller unifies this by providing a single command-line interface that can fetch and inject secrets from any configured backend, allowing developers to stay in their terminal while working with secrets.

Teller suits teams that use multiple secret storage systems and want to standardize how developers access them. It works well in environments where developers need quick, scriptable access to secrets during development and deployment workflows. The tool is particularly valuable for organizations already invested in cloud-native infrastructure where secrets are distributed across different services. Teams should adopt it if they want to reduce context-switching and create a consistent secrets interface across their infrastructure, regardless of which backend stores each secret.

The project shows active development with regular commits addressing bugs and feature requests. The codebase receives ongoing maintenance with fixes applied to reported issues. The maintainers respond to community contributions and incorporate external feedback into the tool's direction. Development activity demonstrates sustained attention to the project's stability and usability.