Upstream software project

mkcert

CLI tool for making locally-trusted development certificates

About mkcert

CLI tool for making locally-trusted development certificates

This project links 6 native package records across 5 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

mkcert repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Debian 12 (Bookworm): 1 package records; Debian 13 (Trixie): 1 package records; Fedora 43: 2 package records; Fedora 44: 1 package records; openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.mkcert: recorded package coverageDebian 12 (Bookworm)1 recordsDebian 13 (Trixie)1 recordsFedora 432 recordsFedora 441 recordsopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
mkcert
Publisher
Not authoritatively mapped
Native package records
6
Operating systems
debian-12, debian-13, fedora-43, fedora-44, opensuse-tumbleweed
License expression
BSD-3-Clause
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

mkcert is a simple tool for making locally-trusted development certificates. It requires no configuration. Using certificates from real certificate authorities (CAs) for development can be dangerous or impossible (for hosts like example.test, localhost or 127.0.0.1), but self-signed certificates cause trust errors. Managing your own CA is the best solution, but usually involves arcane commands, specialized knowledge and manual steps. mkcert automatically creates and installs a local CA in the system root store, and generates locally-trusted certificates. mkcert does not automatically configure servers to use the certificates, though, that's up to you. Warning: the rootCA-key.pem file that mkcert automatically generates gives complete power to intercept secure requests from your machine. Do not share it.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 12 (Bookworm)

  1. Package mkcert

    bookworm (Debian 12 (Bookworm)) (utils): Simple zero-config tool to make locally trusted certificates

    1.4.4-1+b6: amd64 arm64

    Source: mkcert

Debian 13 (Trixie)

  1. Package mkcert

    trixie (Debian 13 (Trixie)) (utils): Simple zero-config tool to make locally trusted certificates

    1.4.4-1+b18: amd64 arm64

    Source: mkcert

Fedora 43

  1. Source: mkcert

  2. Package mkcert

    43 (Fedora 43) (Unspecified): Make and install locally trusted development certificates

    1.4.4-3.fc43: aarch64 x86_64

    Source: mkcert

Fedora 44

  1. Package mkcert

    44 (Fedora 44) (Unspecified): Make and install locally trusted development certificates

    1.4.4-9.fc44: aarch64 x86_64

    Source: mkcert

openSUSE Tumbleweed

  1. Package mkcert

    tumbleweed (openSUSE Tumbleweed) (Development/Tools/Other): CLI tool for making locally-trusted development certificates

    1.4.4-1.7: x86_64

    Source: mkcert

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.