mkcert 0.0.2
Create Self Signed Development Certificates
mkcert@0.0.2 was published on 2018-11-11. Its manifest declares 4 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All mkcert versions · Permanent reference to 0.0.2 · Latest release
Package specifications
| Version | 0.0.2 |
|---|---|
| License declaration | MIT |
| Published | 2018-11-11T09:03:28.299Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 4 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 21.46 KiB |
| Published file count | 9 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | lib/mkcert.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 5 |
| Repository stars | 164 |
| Repository forks | 15 |
Install mkcert 0.0.2
npm install mkcert@0.0.2 pnpm add mkcert@0.0.2 yarn add mkcert@0.0.2
Runtime dependencies
- commander ^2.19.0
- is-ip ^2.0.0
- node-forge ^0.7.6
- random-int ^1.0.0
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- commander@2.20.3 — direct
- ip-regex@2.1.0 — indirect
- is-ip@2.0.0 — direct
- node-forge@0.7.6 — direct
- random-int@1.0.0 — direct
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Binary-Artifacts | 10/10 — no binaries found in the repo |
|---|---|
| Code-Review | 1/10 — Found 4/21 approved changesets -- score normalized to 1 |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| Security-Policy | 0/10 — security policy file not detected |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/mkcert/0.0.2 — retrieved 2026-10-30T02:41:01.141Z
- https://api.deps.dev/v3/projects/github.com%2FSubash%2Fmkcert — retrieved 2026-10-29T12:25:12.822Z (stale snapshot; refresh pending)
- https://api.deps.dev/v3/systems/npm/packages/mkcert/versions/0.0.2 — retrieved 2026-10-30T02:41:01.653Z
- https://api.deps.dev/v3/systems/npm/packages/mkcert/versions/0.0.2:dependencies — retrieved 2026-10-30T02:41:01.673Z