step CLI
v0.28.4 open-sourceThe section your link pointed to isn't on step CLI's page any more, so we've brought you to the top.
CLI tool for building, operating, and automating PKIPKIA framework of policies, roles, and cryptographic standards for issuing and managing digital certificates that bind public keys to identities, letting tools verify authenticity and encrypt communications without pre-shared secrets. systems, X.509X.509A standard defining the format of public-key certificates, maintained by the ITU-T, used by cyber tools to authenticate identities and establish encrypted connections over TLS and similar protocols./SSH certificates, JWTsJWTsJSON Web Tokens — an open standard (RFC 7519) for encoding claims as a signed, optionally encrypted JSON object. Cyber tools use them for stateless authentication without server-side session storage., and OAuth flows.
STEP_OPEN_BROWSER=false step ca token
step ca token --user my-service <sub-claim> <path-to-csr>
step ca renew cert.pem cert.key --kms <kms-id>
step ca rekey cert.pem cert.key --kms <kms-id>
step ca issue example.com example.crt example.key --remove-scope
cat cert.pem | step certificate fingerprint -
step ssh --console <user>@<host>
step rand 16
step crypto jwe decrypt --password-file /run/secrets/jwe_password encrypted.jwt
step certificate create example.com out.crt out.key --set "env=prod" --set-file vars.json
step certificate sign ca.crt ca.key out.crt --kms <kms-type>
step certificate create example.com out.crt out.key --template '{{ .SANs }}'
step ca policy list
step cert inspect ssh_host_cert.pub
step oauth --redirect-uri 'http://localhost:8080/callback'
step oauth --listen 127.0.0.1:9443
step cert inspect <path-to-cert> --check-expiration
step ssh check-host --quiet <hostname>
step ca roots
step ca federation
Summary
step CLI is an open-source command-line tool that builds, operates, and automates Public Key Infrastructure (PKI) systems and workflows. It is licensed under Apache 2.0 and runs as a command-line tool, designed for practitioners needing certificate-management, ACMEACMEAn IETF-standard protocol (RFC 8555) for automating TLS certificate issuance and renewal, letting cyber tools manage certificates without manual CA interaction., or SSH-certificates capabilities. Its documentation positions it alongside tools for general crypto and X.509 operations, and it was first launched in 2016.
CLI tool for building, operating, and automating PKI systems, X.509/SSH certificates, JWTs, and OAuth flows.
How step CLI helps
Is this certificate actually trustworthy and correctly formed before I deploy it?
validates and lints the X.509 certificate against RFC5280 and CA/Browser Forum baseline requirements, flagging fields that would fail elsewhere
Can I get a browser-trusted TLS certificate without standing up my own CA?
requests and retrieves a certificate from Let's Encrypt directly from the command line
Will my system trust the certificates issued by a given CA?
keeps that CA's certificate in, or out of, the system and browser trust store, so trust reflects whatever was last added or removed
What's actually inside this SSH certificate someone handed me?
parses and prints the certificate's identity, principals, and validity period so its claims can be checked before it's relied on
How do I prove two files are identical or that data hasn't been tampered with, without a full PKI?
signs and encrypts the data with the NaCl library and verifies it on the other end
Is this MFA code generator actually going to match what the server expects?
generates and verifies TOTP tokens from a shared secret so both sides can be checked against the same algorithm
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for step CLI, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail step CLI puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Website history
smallstep.com, every changeSmallstep's home page and 10 more pages as they looked each month from September 2021 to October 2026: 25 renders, 4 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
19 entries
No entries match these filters.
- March 20251
- February 20251
- October 20242
- September 20241
- July 20241
- June 20241
- November 20231
- August 20221
- July 20221
- May 20221
- April 20221
- March 20221
- November 20211
- October 20211
- July 20211
- April 20211
- March 20211
- January 20191
Project health
Issue, contributor and maintainer activity in smallstep/cli, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 7 −5 vs prior 12 months
- Maintainers 4 +2 joined · −1 left, last 12 months
- Bus factor 2 committers behind half the commits
- Community-filed 96% of issues opened, last 12 months
- Median time to close 57 days first maintainer reply 10 days
- Open backlog 154 of 499 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 154
- Contributors / month 1
- Commits / month 4
- Stars 4,330
- bugs 50%
- features 41%
- other 9%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.