npm Package Name Checker
Type a name and this asks registry.npmjs.org whether a package has it. A 404 is not the whole answer: npm refuses a new name that differs from an existing one only by punctuation, so react_dom fails because react-dom exists, and it refuses Node.js core module names such as fs and http. The box checks both. New names are lower case, up to 214 characters, and cannot start with a period, hyphen or underscore. A scoped name such as @you/tool sidesteps all of this: only the owner of the @you scope can publish under it.
Free, no sign-in, 20 checks a minute. Checks the package name on npm plus the .com, .dev, .io. All four registries and GitHub at once.
npm name rules
- Lower case only for new packages; this checker lowers what you type.
- Up to 214 characters, the @scope/ part included.
- Letters a-z, digits, hyphen, period and underscore; no spaces and none of ~ ' ! ( ) *.
- Does not start with a period, hyphen or underscore.
- Not a Node.js core module name (fs, http, path, events, crypto...) and not node_modules or favicon.ico.
A name that breaks these is reported as not allowed without asking npm.
12 names on npm
Checked on November 11, 2026 from one US connection, with the same code this tool runs. Free here: red-cloth, tidefold. Click a name to check it live.
What taken and free mean on npm
Too similar is checked from your spelling outward
npm compares names with . _ and - removed. The box asks for the hyphenated and the punctuation-free spellings of what you type, which catches react_dom (react-dom exists) and ex-press (express). The other direction cannot be asked by name: if you type mytool and someone owns my-tool, no lookup finds that, and npm publish answers 403 with a too similar error.
A fresh unpublish still holds the name
After every version of a package is unpublished, npm blocks new versions under that name for 24 hours. The registry keeps a record of the unpublished package, so it reads as taken here until then.
Taken often means abandoned
Many short names belong to packages that have not shipped in years: npm's requests last shipped 0.3.0 in 2019, and its tokio 0.1.2 in 2018. The reliable route to one is asking its owner to add you as a maintainer. Otherwise, publish under your own scope (@you/tokio) and keep the exact word.
npm name questions
How do I check if an npm package name is available?
Type it in the box at the top of this page: it asks the npm registry for the name, then for its hyphenated and punctuation-free spellings, and tells you whether npm would accept it. From a terminal, npm view <name> prints the package if it exists and fails with E404 if it does not, but it does not test the too similar rule, which only npm publish enforces.
Why does npm say my package name is too similar to an existing package?
Because npm compares a new name with every existing one after removing periods, hyphens and underscores, to stop typosquats such as reactdom next to react-dom. npm publish answers 403 Forbidden, names the package it collides with and suggests publishing under your scope instead. The scoped name, @you/react_dom, is always allowed, since only you can publish under @you.
Can npm package names have capital letters?
Not new ones. npm has required lower case for new packages for years, and npm publish refuses a name with a capital letter. Older packages from before the rule keep theirs: JSONStream was downloaded over 14 million times in the first week of November 2026 under that spelling. This checker lowers what you type, so checking MyLib checks mylib.
How do I publish a scoped package publicly?
Set the name to @you/name in package.json, where @you is your npm username or an organization you belong to, and run npm publish --access public. Scoped packages are private by default, and a free account cannot publish private ones, so the first publish without --access public fails. After that, the access setting sticks for later versions.
Can I take the name of an unpublished npm package?
Only after 24 hours, and only if every version was unpublished. npm lets owners unpublish within 72 hours of publishing, or later only when nothing in the public registry depends on the package, it had under 300 downloads in the last week and it has a single owner. A package that passes those tests and is fully unpublished blocks its name for a day.
Check the rest of the name
Check the name on all four registries at once, or on PyPI, crates.io or RubyGems. The same name as a handle: the GitHub username checker, or the username checker for 15 platforms at once. No name yet? The startup name generator, brand name generator and business name generator check the .com of every idea live as they write it. For the domain alone, the domain availability checker asks the registry live.