npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

namescout-cli

v0.1.1

Published

Check whether a name is available across domains, package registries, code hosts, and plugin marketplaces.

Readme

namescout-cli

Check whether a project, package, or product name is available across domains, package registries, code hosts, and plugin marketplaces — from your terminal.

npx namescout-cli redis
NameScout · checking "redis" (developer-tool)

Score  11 / 100   Name collision risk

DOMAINS
  ✗  redis.com  taken       DNS records found
  ✓  redis.dev  available   No DNS record found
  ...

PACKAGE REGISTRIES
  ✗  npm        taken       Exact npm package exists
  ...

NEXT STEPS
  → Buy redis.dev first
  → Pick a package-name variant
  → Review GitHub namespace collision

Full report: https://namescout.dev/?q=redis&mode=developer-tool

Install

No install needed:

npx namescout-cli <name>

Or install globally:

npm install -g namescout-cli
namescout <name>

Usage

namescout <name> [options]

Options

| Option | Description | | ----------------- | -------------------------------------------------- | | --mode <mode> | Search mode (default: developer-tool) | | --json | Output raw JSON instead of the formatted report | | --no-color | Disable ANSI colors | | -v, --version | Print version | | -h, --help | Show help |

Modes

  • developer-tool — package registries first
  • saas-product — domains and brand surfaces first
  • library-framework — package and GitHub collisions first
  • extension-plugin — marketplaces and publisher names first

Examples

# Default scan
npx namescout-cli vidpipe

# Different mode
npx namescout-cli my-app --mode saas-product

# Pipe JSON to jq
npx namescout-cli my-tool --json | jq .verdict.score

Environment

| Variable | Description | | ---------------- | --------------------------------------------------------------------- | | NAMESCOUT_API | Override the API base URL (default: https://namescout.dev) | | NO_COLOR | Disable ANSI colors |

Requirements

  • Node.js 18 or newer

Why

Naming a project means checking npm, PyPI, GitHub, Docker Hub, six TLDs, VS Code Marketplace, Homebrew, crates.io, and a dozen other surfaces. NameScout runs them all in one shot and tells you which collisions matter for what you're building.

Web

Same product as the CLI, with a richer report and shareable URLs: namescout.dev.

License

MIT