the terminal companion to namescout.dev. same checks, same scoring, same providers, no browser needed. one command, one report, straight in the shell.
npx namescout-cli rediswhat it does
- hits 12+ providers in parallel: domains, npm, pypi, crates.io, rubygems, packagist, homebrew, docker hub, github, vs code marketplace
- mode-weighted scoring so the verdict matches what you’re building
(
saas-product,developer-tool,library-framework,extension-plugin) - optional ai-assisted alternative-name suggestions via
--suggest - raw json output for piping into
jqor whatever - zero dependencies. node 18+ stdlib only. respects
NO_COLOR.
install
no install needed:
npx namescout-cli <name>or install globally:
npm install -g namescout-cli
namescout <name>examples
# default scan (developer-tool mode)
npx namescout-cli vidpipe
# saas mode, domains weighted higher
npx namescout-cli my-app --mode saas-product
# include alternative-name suggestions
npx namescout-cli my-tool --suggest --count 12
# pipe json to jq
npx namescout-cli my-tool --json | jq .verdict.scoreflags
| flag | what it does |
|---|---|
--mode <mode> | search mode (default: developer-tool) |
--suggest | also generate alternative names via the suggest api |
--count <n> | number of suggestions when using --suggest (1–20, default 8) |
--json | raw json instead of the formatted report |
--no-color | disable ansi colors (also honored via NO_COLOR env var) |
-v, --version | print version |
-h, --help | show help |
NAMESCOUT_API env var overrides the api base url if you self-host.
why a cli
the web report at namescout.dev is the richer
surface. it has the per-provider explanations, near-matches, and a
shareable url. the cli is for the moment when you’re already in the
terminal, already typing npm init, and you don’t want to context-switch
to a browser just to find out the name’s been taken since you thought of
it yesterday.