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

@cmgriffing/isittaken

v0.1.0

Published

Honest multi-registry package-name availability checks for humans and agents.

Readme

isittaken

Honest, multi-registry package-name availability checks — for humans and agents.

isittaken checks bare or venue-qualified names across nine package registries and reports one verdict per venue: available, taken, invalid, or unknown. unknown is never presented as available, so an available verdict always means a definitive "no package found here."

Install

# run it without installing
npx @cmgriffing/isittaken check my-package
# or: pnpm dlx @cmgriffing/isittaken check my-package

# or install globally
npm install -g @cmgriffing/isittaken

Requires Node 22.12 or newer.

Usage

isittaken check <names...> [options]

isittaken check my-package
isittaken check "fuzzy picker" other-name --json   # phrases normalized per venue
isittaken check mylib -r npm,pypi,crates           # scope to exact-only venues
isittaken check symfony/console -r packagist       # qualified input -> exact check

| Option | Meaning | Default | | ---------------------- | ------------------------------------------- | --------------- | | -r, --registry <ids> | comma-separated venue ids to scope the run | all nine venues | | --json | machine-readable JSON (preferred by agents) | human table | | --concurrency <n> | max concurrent lookups per venue | 10 | | --timeout <ms> | per-venue lookup timeout | 10000 |

Venues

  • Exact, definitive checks — npm, pypi, crates, rubygems, nuget, hex
  • Fuzzy for bare words — maven, go, packagist: results carry fuzzy: true; qualified input (e.g. symfony/console) upgrades them to exact checks

Go bare-word search is best-effort and honestly reports unknown when pkg.go.dev rate-limits the client.

JSON output

--json is agent-first: a top-level summary rollup answers "what can I claim?" directly — anyAvailable, per-status counts, and an available list mapping each input to its exact venues (definitive) and its fuzzyVenues (search-index leads to verify).

Non-JSON runs stream per-venue progress checkpoints to stderr while stdout stays clean; --json output is never mixed with progress. Color is automatic and disabled for piped output (NO_COLOR honored).

Exit codes

| Code | Meaning | | ---- | ------------------------------------------------ | | 0 | at least one (name, venue) result is available | | 1 | no name was available at any venue | | 2 | usage error |

Scope notes

  • npm scope claimability is intentionally unsupported: npm provides no dependable signal, so scoped targets are reported invalid per venue.
  • Availability is observed, not guaranteed — each venue remains the authority. Verify on the venue before publishing.
  • Every outbound request carries an identifying User-Agent: isittaken/<version> (+https://github.com/cmgriffing/isittaken).

License

MIT © Chris Griffing. See LICENSE.