smallstep/certificates

🛡️ A private certificate authority (X.509 & SSH) & ACME server for secure automated certificate management, so you can use TLS everywhere & SSO for SSH.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 13 minutes ago
Added to GitGenius on September 7th, 2026
Created on November 1st, 2018
Open Issues & Pull Requests: 296 (+0)
GitHub issues: Enabled
Number of forks: 590
Total Stargazers: 8,843 (+0)
Total Subscribers: 84 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 43.3 hours
Mean response time: 17.2 days
90th percentile: 24.0 days
Tracked items: 192

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 93% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 74% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 4% of issues opened in the past year have been closed. Three people close 62% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 122
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 723 days
Stale 30+ days: 115
Stale 90+ days: 101

Recent activity

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

Top labels

  • needs triage (157)
  • bug (78)
  • enhancement (78)
  • good first issue (3)
  • roadmap (3)
  • area/acme (2)
  • documentation (2)
  • quickfix (2)

Detailed Description

step-ca is a private certificate authority and ACME server for automated certificate management across DevOps infrastructure.

The tool addresses the complexity of setting up a public key infrastructure by providing an online CA that automates certificate issuance and renewal. It works by acting as both an X.509 certificate authority for HTTPS and TLS, and an SSH certificate authority, while also implementing the ACME protocol to enable automated certificate provisioning. This dual capability means teams can use a single system to issue browser-valid HTTPS certificates, TLS certificates for infrastructure components like containers and Kubernetes pods, and SSH certificates for both user authentication via single sign-on and host authentication via cloud instance identity documents.

The tool suits small to medium teams building DevOps infrastructure who need certificate automation without the complexity of a full enterprise PKI. It works well for organizations automating certificate management across VMs, containers, APIs, and Kubernetes environments. The README identifies its optimization for two-tier PKI serving common DevOps use cases and notes that teams requiring multiple certificate authorities, active revocation mechanisms like CRL or OCSP, high-volume high-availability setups, device identity and attestation, fine-grained role-based access control, or deep identity provider integration should consider the commercial offering instead.

The project maintains active community engagement through discussions and Discord, with documentation covering installation, ACME basics, and challenge types. Development appears focused on supporting the core use cases of automated certificate issuance and renewal for DevOps workflows, with the tool designed to integrate with existing infrastructure through its Go wrapper library and command-line client companion.