pickfit

BrowseSecurity & networking tools

mkcert

Command-line tool that creates a local certificate authority, installs it in system and browser trust stores, and generates locally trusted development certificates.

Use it

Before you install: known vulnerabilities

pickfit found 17 known high or critical vulnerabilities in the packages a fresh install brings (OSV.dev, 16 Nov 2026). Weigh this before you install it.

  • go:golang.org/x/crypto v0.0.0-20220331220935-ae2d96664a29 golang.org/x/crypto vulnerable to auth bypass via unenforced @revoked status (GHSA-5cgq-3rg8-m6cv, critical, fixed in 0.52.0)
See 9 more
  • go:golang.org/x/crypto v0.0.0-20220331220935-ae2d96664a29 — GHSA-89gr-r52h-f8rx (critical), fixed in 0.52.0
  • go:golang.org/x/crypto v0.0.0-20220331220935-ae2d96664a29 — GHSA-f5wc-c3c7-36mc (critical), fixed in 0.52.0
  • go:golang.org/x/crypto v0.0.0-20220331220935-ae2d96664a29 — GHSA-jppx-rxg9-jmrx (critical), fixed in 0.52.0
  • go:golang.org/x/crypto v0.0.0-20220331220935-ae2d96664a29 — GHSA-rm3j-f69w-wqmq (critical), fixed in 0.52.0
  • go:golang.org/x/crypto v0.0.0-20220331220935-ae2d96664a29 — GHSA-v778-237x-gjrc (critical), fixed in 0.31.0
  • go:golang.org/x/crypto v0.0.0-20220331220935-ae2d96664a29 — GHSA-vgwf-h737-ff37 (critical), fixed in 0.52.0
  • go:golang.org/x/crypto v0.0.0-20220331220935-ae2d96664a29 — GHSA-x527-x647-q7gg (critical), fixed in 0.52.0
  • go:golang.org/x/crypto v0.0.0-20220331220935-ae2d96664a29 — GHSA-hcg3-q754-cr77 (high), fixed in 0.35.0
  • go:golang.org/x/crypto v0.0.0-20220331220935-ae2d96664a29 — GHSA-q4h4-gmj2-qvw2 (high), fixed in 0.52.0

7 more findings not listed here.

Linux x86_64

You need first

  • Runtimes: go>=1.13 (build from source only)
  • System packages: certutil (libnss3-tools / nss-tools / nss) on Linux, nss on macOS for Firefox
  1. Download the prebuilt linux/amd64 binary, chmod +x it and copy it to ~/.local/bin/mkcert

    curl -fJLO "https://dl.filippo.io/mkcert/latest?for=linux/amd64" && chmod +x mkcert-v*-linux-amd64 && mkdir -p ~/.local/bin && cp mkcert-v*-linux-amd64 ~/.local/bin/mkcert

Check that it works

mkcert -version

The output should contain “v1.4.4”.

First thing to try

mkcert example.com "*.example.com" example.test localhost 127.0.0.1 ::1

Run mkcert <name> with the domains or IPs you want a certificate for, such as mkcert localhost 127.0.0.1.

What it does

  • Create certificates for several names, wildcards and IPs
    How to use it
    1. Run mkcert <domain> "*.<domain>" localhost 127.0.0.1 ::1 with the names and IPs you need.
    2. Find the new certificate and key files in the current folder.
    Tested
  • Create client, ECDSA or PKCS #12 certificates
    How to use it
    1. Run mkcert -client -ecdsa -pkcs12 <domain>.
    2. Find the PKCS #12 bundle at ./<domain>-client.p12.
    Tested
  • Sign a certificate from your own CSR
    How to use it
    1. Create a certificate signing request file, for example with openssl.
    2. Run mkcert -csr <file>.
    3. Find the signed certificate in the current folder.
    Tested
  • Install a local CA into system and browser trust stores
    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

  • serve localhost over HTTPS without browser trust errors
  • generate an S/MIME certificate for an email address
  • make Node.js trust local development certificates

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 v1.4.4

Differences the test machine hit

  • README: sudo cp mkcert-v*-linux-amd64 /usr/local/bin/mkcert
    In the test: Copied the binary to ~/.local/bin/mkcert instead, because the box has no sudo
  • README: On Linux, first install certutil (sudo apt install libnss3-tools)
    In the test: Not needed to make certificates. certutil is only used by -install for the NSS/Firefox store, and it could not be installed here without root

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.