npm-namer

Finds available npm package names. Bundles a Node script (scripts/npm-namer/dist/check.mjs) that runs four layers of check:

1. Syntactic validation — thin wrapper over the official validate-npm-package-name package (uppercase, leading char, length, URL-safe, core-module shadow, etc.)
2. Availability — parallel HEAD requests to registry.npmjs.org for each candidate
3. Moniker collision — npm's publish-time rule (lowercase + strip .-_); catches estoolkit colliding with es-toolkit
4. Near-match (typosquat) warning — Damerau-Levenshtein distance against the top ~15,000 most-downloaded npm packages (TypoGard's published threshold, sourced from nice-registry/download-counts); catches extoolkit as suspiciously close to es-toolkit even though it would publish fine per the moniker rule

The full rule set the script encodes is in references/moniker-rules.md — load that when the user asks why a name fails.

Inputs

$ARGUMENTS — one of:

• Seeds + concept: "i want a tiny logging lib. seeds: tinylog, microlog, jslog" → permute + check
• Concept only: "name a cli that queries bigquery in the terminal" → brainstorm seeds, then permute + check
• Pre-checked list: "are these taken? a, b, c, d" → batch check only, no brainstorming
• Empty → ask what kind of package needs naming