# Install mkcert with npm

Create Self Signed Development Certificates. Version 3.2.0 via npm; verified 2023-11-07.

## Install

```sh
sudo av install npm:mkcert
```

Additional install commands:

### Portable and language managers

- npm (100%):

```sh
npm install -g mkcert
```

  Evidence: local npm package metadata

## Package facts

- **Package key:** npm:mkcert
- **Package manager:** npm
- **Package manager page:** <https://www.npmjs.com/package/mkcert>
- **Version:** 3.2.0
- **Source summary:** Create Self Signed Development Certificates
- **Homepage:** <https://github.com/Subash/mkcert#readme>
- **Repository:** <https://github.com/Subash/mkcert>
- **Upstream docs:** <https://github.com/Subash/mkcert#readme>
- **License:** MIT
- **Source archive:** <https://registry.npmjs.org/mkcert/-/mkcert-3.2.0.tgz>
- **Issue tracker:** <https://github.com/Subash/mkcert/issues>
- **Published:** 2023-11-07T14:04:58.390Z
- **Last updated:** 2023-11-07T14:04:58.390Z
- **Generated:** 2026-07-08T07:18:31+00:00

## Executables

- mkcert (cli)

## Dependencies

- commander
- node-forge

## Build dependencies

- @types/node-forge
- jest
- prettier
- ts-jest
- typescript

## Install behavior

- Post-install hook: not defined
- Bottle: not available

## Freshness

- Page generated: 2026-07-08
- Package-manager version: 3.2.0
- Package-manager updated: 2023-11-07
- Local data: ok
- Upstream repository: https://github.com/Subash/mkcert
- warning: The package-manager record has not been updated in over a year.
- info: No cached GitHub release or tag data was available.

## Security Notes

No matching local secret-handling manifest was found for mkcert. Nucleus package metadata is still published here so future coverage has a stable package URL.


## Source Database Details

- **Source Database:** npm registry
- **Dist Tags:** Latest: 3.2.0
- **Version Count:** 16
- **Maintainers:** sbspk
- **Author:** Subash Pathak
- **Publisher:** sbspk
- **Engines:** Node: >=16
- **Integrity:** sha512-026Eivq9RoOjOuLJGzbhGwXUAjBxRX11Z7Jbm4/7lqT/Av+XNy9SPrJte6+UpEt7i+W3e/HZYxQqlQcqXZWSzg==
- **Shasum:** 6c4d58bbb31dbf76efd24f197d454702b14020f4
- **Unpacked Size:** 11,923
- **File Count:** 0
- **Created At:** 2018-11-11T08:56:22.129Z
- **Latest Published At:** 2023-11-07T14:04:58.390Z
- **Modified At:** 2023-11-07T14:04:58.562Z

## Other Package-Manager Records

- Debian apt - mkcert - 1.4.4-1+b18: normalized package name match | Debian stable package indexes: mkcert from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | Simple zero-config tool to make locally trusted certificates | https://github.com/FiloSottile/mkcert
- Nix - mkcert: normalized package name match | nixpkgs package indexes: pkgs/by-name/mk/mkcert/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- Ubuntu apt - mkcert - 1.4.4-1ubuntu2: normalized package name match | Ubuntu 24.04 LTS package indexes: mkcert from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | Simple zero-config tool to make locally trusted certificates | https://github.com/FiloSottile/mkcert
- apk - mkcert - 1.4.4-r29: normalized package name match | Alpine Linux edge package indexes: mkcert from https://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz | simple zero-config tool to make locally trusted development certificates with any names you'd like | https://mkcert.dev/
- dnf - mkcert - 1.4.4-9.fc45: normalized package name match | Fedora Rawhide package metadata: mkcert from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/e5ca8ce900cd68f5419e1c39ae517343100b306336cbaeb70a3c153121d95094-primary.xml.zst | Make and install locally trusted development certificates | https://github.com/FiloSottile/mkcert
- pacman - mkcert - 1.4.4-3: normalized package name match | Arch Linux sync databases: mkcert from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | Simple tool for making locally-trusted development certificates | https://github.com/FiloSottile/mkcert
- zypper - mkcert - 1.4.4-1.4: normalized package name match | openSUSE Tumbleweed package metadata: mkcert from https://download.opensuse.org/tumbleweed/repo/oss/repodata/be8d3611d25469107f32075a1697e69ec57a2b850b42348a658cc671ad5ec2b50760d02c3e59524d50da9a11d5be799bdaffba2e166e8ca8858512e3c0bd665d-primary.xml.zst | CLI tool for making locally-trusted development certificates | https://github.com/FiloSottile/mkcert
- MacPorts - mkcert: normalized package name match | MacPorts ports tree: security/mkcert/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
- Chocolatey - mkcert: normalized package name match | Chocolatey community package catalog: mkcert from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','mirc'
- Scoop - extras/mkcert: normalized package name match | Scoop official bucket manifest trees: bucket/mkcert.json from https://api.github.com/repos/ScoopInstaller/Extras/git/trees/master?recursive=1
- winget - FiloSottile.mkcert: normalized package name match | Windows Package Manager source index: FiloSottile.mkcert from https://cdn.winget.microsoft.com/cache/source.msix


## Related links

- [Language runtime packages](https://www.automicvault.com/pkg/language-runtime-packages/) - Matched curated package taxonomy and local package facts.
- [mkcert](https://www.automicvault.com/pkg/brew/mkcert/) - Same normalized package name appears in another local ecosystem. Shared terms: certificates, development, mkcert.
- [office-addin-dev-certs](https://www.automicvault.com/pkg/npm/office-addin-dev-certs/) - Local package facts share a topical domain. Shared terms: cert, certificates, commander, development, mkcert.
- [create-medusa-app](https://www.automicvault.com/pkg/npm/create-medusa-app/) - Both packages touch the same language runtime or ecosystem. Shared terms: commander, create, node.
- [mkcert](https://www.automicvault.com/pkg/brew/mkcert/) - Same normalized package name exists in another local package ecosystem.

## Sources

- Nucleus package database
- package-page enrichment
- package version freshness
- package relationship graph
- external package-manager database matches
- cross-ecosystem install command graph
