smallstep/cli

🧰 A zero trust swiss army knife for working with X509, OAuth, JWT, OATH OTP, etc.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 25 minutes ago
Added to GitGenius on September 16th, 2026
Created on July 17th, 2018
Open Issues & Pull Requests: 195 (+0)
GitHub issues: Enabled
Number of forks: 320
Total Stargazers: 4,332 (+0)
Total Subscribers: 57 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.3 days
Mean response time: 59.8 days
90th percentile: 64.5 days
Tracked items: 89

Most active contributors

Sign in to see contributor activity.

How this project is maintained

83% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 82% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 70
New in 7 days: 2
Closed in 7 days: 1
Avg open age: 939 days
Stale 30+ days: 63
Stale 90+ days: 62

Recent activity

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

Top labels

  • needs triage (74)
  • enhancement (50)
  • bug (39)
  • good first issue (9)
  • docs (2)
  • help wanted (2)
  • UX (1)
  • area/CICD (1)

Detailed Description

Smallstep CLI is a command-line tool for working with X.509 certificates, OAuth, JWT, OATH OTP, and related cryptographic primitives in zero trust architectures.

The tool addresses the complexity of managing multiple authentication and encryption standards by providing a unified interface for common operations across these domains. Rather than requiring separate tools for certificate inspection, JWT validation, OAuth flows, and one-time password generation, the CLI consolidates these capabilities into a single executable. This approach reduces context-switching and simplifies scripting and automation workflows that touch multiple security protocols.

The tool suits developers and operators building zero trust systems who need to inspect, create, or validate credentials across different formats and standards. It is particularly valuable in environments where certificate management, token handling, and multi-factor authentication setup occur frequently. The README positions this as a general-purpose utility rather than a specialized replacement for domain-specific tools, making it most useful as a complement to existing security infrastructure rather than a wholesale alternative.

Development activity shows consistent engagement with the codebase through regular commits addressing bug fixes and feature additions. The project maintains responsiveness to user-reported issues, with maintainers actively triaging and resolving problems. Pull requests receive timely review and feedback, indicating an active development cycle. The maintainers demonstrate attention to code quality and testing practices throughout the repository's history.