# mkcert mit npm installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für mkcert in AI-Agent-Workflows.

## Installation

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

Weitere Installationsbefehle:

### Portable und Sprach-Paketmanager

- npm (100%):

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

  Evidenz: local npm package metadata

## Paketfakten

- **Paketschlüssel:** npm:mkcert
- **Paketmanager:** npm
- **Paketmanager-Seite:** <https://www.npmjs.com/package/mkcert>
- **Version:** 3.2.0
- **Quellzusammenfassung:** Create Self Signed Development Certificates
- **Homepage:** <https://github.com/Subash/mkcert#readme>
- **Repository:** <https://github.com/Subash/mkcert>
- **Upstream-Dokumentation:** <https://github.com/Subash/mkcert#readme>
- **Lizenz:** MIT
- **Quellarchiv:** <https://registry.npmjs.org/mkcert/-/mkcert-3.2.0.tgz>
- **Issue-Tracker:** <https://github.com/Subash/mkcert/issues>
- **Veröffentlicht:** 2023-11-07T14:04:58.390Z
- **Zuletzt aktualisiert:** 2023-11-07T14:04:58.390Z
- **Generiert:** 2026-08-04T22:13:35+00:00

## Executables

- mkcert (cli)

## Abhängigkeiten

- commander
- node-forge

## Build-Abhängigkeiten

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

## Installationsverhalten

- Post-install-Hook: nicht definiert
- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-04
- Manager-Version: 3.2.0
- Manager aktualisiert: 2023-11-07
- lokale Daten: OK
- Upstream-Repository: https://github.com/Subash/mkcert
- Warnung: The package-manager record has not been updated in over a year.
- Info: No cached GitHub release or tag data was available.

## Sicherheitshinweise

Für mkcert wurde kein passendes lokales Secret-Handling-Manifest gefunden. Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.


## Details aus der Quelldatenbank

- **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

## Andere Paketmanager-Einträge

- 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-r30: 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-10.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/210a2053c8e007daf9ae39c2a21daaed9b2ddd07d63ecffa597050361e73650c-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.7: normalized package name match | openSUSE Tumbleweed package metadata: mkcert from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-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','microsoft-windows-terminal'
- 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


## Verwandte Links

- [Security and crypto packages](https://pkg.so/de/security-crypto-tools/) - Matched curated package taxonomy and local package facts.
- [mkcert](https://pkg.so/de/brew/mkcert/) - Same normalized package name appears in another local ecosystem. Shared terms: certificates, cli, development, mkcert, security.
- [ssl-checker](https://pkg.so/de/npm/ssl-checker/) - Both packages touch the same language runtime or ecosystem. Shared terms: certificate, certificates, cli, node, security.
- [certstrap](https://pkg.so/de/brew/certstrap/) - Security-sensitive metadata or terminology overlaps. Shared terms: certificate, certificates, cli, security, signed.
- [mkcert](https://pkg.so/de/brew/mkcert/) - Same normalized package name exists in another local package ecosystem.

## Quellen

- pkg.so package database
- package-page enrichment
- package version freshness
- pkgdb category and tag curation
- package relationship graph
- external package-manager database matches
- cross-ecosystem install command graph
