pickfit

BrowseSecurity & networking tools

Step CLI

Command-line tool for building, operating and automating PKI workflows, X.509 and crypto operations, and a client for the step-ca certificate authority.

Tested on Linux

Use it

Linux x86_64

  1. download and extract official step_linux_amd64 tarball

    mkdir -p ~/.local/bin /tmp/step && curl -fsSL -o /tmp/step/step.tgz https://dl.smallstep.com/cli/docs-cli-install/latest/step_linux_amd64.tar.gz && tar -xzf /tmp/step/step.tgz -C /tmp/step
  2. install binary into ~/.local/bin and print version

    install -m 755 /tmp/step/step_linux_amd64/bin/step ~/.local/bin/step && step version

Check that it works

install -m 755 /tmp/step/step_linux_amd64/bin/step ~/.local/bin/step && step version

The output should contain “Smallstep CLI/0.31.0 (linux/amd64)”.

First thing to try

install -m 755 /tmp/step/step_linux_amd64/bin/step ~/.local/bin/step && step version

Run step version to confirm it works, then step help to see the available commands.

What it does

  • Create, revoke, check and bundle X.509 certificates
    How to use it
    1. Create a root CA with step certificate create "<root name>" root.crt root.key --profile root-ca --no-password --insecure -f, then a leaf with `step certificate create <hostname> leaf.crt leaf.key --
    2. Check the leaf against the root with step certificate verify leaf.crt --roots root.crt.
    3. Bundle the certificates with step certificate bundle leaf.crt root.crt bundle.crt and view one with step certificate inspect leaf.crt --short.
    Tested
  • Run and use a step-ca or ACME certificate authority
    How to use it
    1. Set up a new CA with step ca init --ssh --name <CA name> --dns <hostname> --address <ip:port> --provisioner <email> --password-file <file> --deployment-type standalone.
    2. Look for the message "Your PKI is ready to go."
    3. Run step help ca to see how to issue certificates for your services.
    Tested
  • Work with JWTs and JOSE objects
    How to use it
    1. Create a key pair with step crypto jwk create pub.json priv.json --kty EC --no-password --insecure -f.
    2. Sign a token with step crypto jwt sign --key priv.json --iss <issuer> --aud <audience> --sub <subject> --exp <unix time> < /dev/null > <file>.
    3. Verify it with step crypto jwt verify --key pub.json --iss <issuer> --aud <audience> < <file>.
    Tested
  • Create and manage SSH certificates
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 3 of 4 features work
  4. Works offline

macOS and Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • inspect a remote server's TLS certificate
  • sign, verify and inspect JWTs
  • generate and verify TOTP tokens
  • get OAuth access tokens at the command line

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 15 Nov 2026
  • Version Smallstep CLI/0.31.0

Differences the test machine hit

  • README: apt-get / dnf / pacman / apk install step-cli (run as root)
    In the test: No root here; used the official Linux binary tarball from dl.smallstep.com/cli/docs-cli-install/latest/step_linux_amd64.tar.gz and copied bin/step to ~/.local/bin
  • README: step certificate inspect https://smallstep.com
    In the test: Works (cmd 3) but needs network access, so not cited as an offline smoke test
  • README: step crypto jwt sign (payload optional)
    In the test: Without a payload argument it waits on stdin; redirect < /dev/null when non-interactive
  • README: step ssh certificate with offline step-ca
    In the test: Offline mode prompts on /dev/tty for the CA key password; had to add "password" to $STEPPATH/config/ca.json for non-interactive use

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.