Package Name Checker
Type a name to ask npm, PyPI, crates.io and RubyGems at once whether a package already has it, and whether the registry would refuse it anyway. Free is not always publishable: npm and PyPI refuse a name that matches an existing package once . _ and - are removed, PyPI refuses Python standard library module names, crates.io reserves names like std, and RubyGems refuses lookalikes of popular gems. The box checks all of those, then the same name as a GitHub username and as a .com, .dev and .io. On 11 November 2026, react was taken on all four registries, while tokio was still free on RubyGems and lodash on crates.io.
Free, no sign-in, 20 checks a minute. Checks npm, PyPI, crates.io and RubyGems, the GitHub username, and the .com, .dev, .io. One registry only: npm, PyPI, crates.io, RubyGems.
12 package names on four registries
Checked on November 11, 2026 from one US connection, with the same code this tool runs. 4 of the 12 were taken everywhere; famous names are often free in another ecosystem. Click a name to check it live.
| Name | npm | PyPI | crates.io | RubyGems |
|---|---|---|---|---|
| react | Taken, 19.3.1 | Taken, 4.3.0 | Taken, 0.1.0 | Taken, 0.1.0 |
| requests | Taken, 0.3.0 | Taken, 2.34.2 | Taken, 0.0.30 | Taken, 1.0.2 |
| serde | Taken | Taken, 0.9.0 | Taken, 1.0.229 | Taken, 0.0.9 |
| rails | Taken, 4.1.0-beta | Taken, 0.0.5 | Taken, 0.1.0 | Taken, 8.1.4.1 |
| express | Taken, 5.3.0 | Free | Taken, 0.0.2 | Taken, 0.0.1 |
| tokio | Taken, 0.1.2 | Taken, 0.2.0 | Taken, 1.54.1 | Free |
| pandas | Taken, 0.0.3 | Taken, 3.1.1 | Free | Taken, 0.3.8 |
| lodash | Taken, 4.18.1 | Taken, 0.0.1 | Free | Free |
| json | Taken, 11.0.0 | Reserved | Taken, 0.12.4 | Taken, 3.1.0 |
| fast_api | Too similar to fast-api | Too similar to fastapi | Free | Too similar to fastapi |
| red-cloth | Free | Free | Free | Too similar to RedCloth |
| tidefold | Free | Free | Free | Free |
Taken shows the latest version. fast_api has no package of its own on npm, PyPI or RubyGems, yet all three would refuse it; red-cloth is free everywhere except RubyGems, where RedCloth owns it. json is refused on PyPI as a standard library module, while asyncio and typing were claimed before that rule.
Package name rules by registry
| Rule | npm | PyPI | crates.io | RubyGems |
|---|---|---|---|---|
| Length | 214 | no length rule | 64 | 255 |
| Characters | a-z 0-9 - . _ | A-Z a-z 0-9 - . _ | A-Z a-z 0-9 - _ | A-Z a-z 0-9 - . _ |
| Case | lower case only | ignored | ignored | ignored for uniqueness |
| Same name | exact | . _ - runs are one | - equals _ | case-insensitive |
| Lookalikes refused | same without . _ - | same without . _ -, l/i=1, o=0 | none | same without - _ (popular or recent gems) |
| Reserved | Node core modules | stdlib modules, admin list | Rust project names | org name and prefix reservations |
Read from each registry's own source code on November 11, 2026. A name that breaks a rule is reported as not allowed without asking the registry.
Package name questions
How do I check if a package name is available?
Type it in the box at the top of this page. domhaul asks each registry's own API for the name (registry.npmjs.org, pypi.org, crates.io and rubygems.org), then applies the rules each one enforces at publish time, so a name that no package has but the registry would still refuse shows as similar or reserved instead of free. Nothing is published or reserved, and you do not need an account on any of them.
Why is a name free on one registry and taken on another?
Each registry is its own namespace, and owning a name on one gives no claim on the others. The react on PyPI is an unrelated project whose last release was in 2018, and the react crate on crates.io is a 0.1.0 last updated in 2015. Of the 12 names in the table below, 4 were taken on all four registries on 11 November 2026, while express was still free on PyPI and pandas on crates.io. If you plan to ship bindings for several languages, check all four before you announce the name.
What does similar mean in the results?
No package has the exact name, but the registry would refuse it because it collides with one that does. npm and PyPI compare names with . _ and - removed, so fast_api fails on both because fast-api and fastapi exist. RubyGems ignores case and removes - and _, and refuses the name if the gem it matches has 10,000 or more downloads or a release in the last five years. The result names the package it collides with and links to it.
Can I reserve a package name without publishing?
No. All four registries hand a name to the first successful publish, with no reservation step: even a PyPI trusted publisher set up for a project that does not exist yet does not hold the name, and is invalidated if someone else uploads first. Publishing an empty placeholder only to hold a name counts as squatting under PyPI's PEP 541 and the crates.io usage policy, and can be removed. Publish a small working 0.0.1 instead.
Should the package name match the GitHub repo and the domain?
It helps people find you, and it costs nothing to check now. Registries link the package page to its repository, so a package called tidefold that lives at github.com/someone-else/tf-core looks like a fork. A matching .dev domain is the usual home for docs: .dev is on browsers' HSTS preload list, so it only ever loads over https. The box checks the GitHub username (users and organizations share one namespace) and the .com, .dev and .io for the same name.
Check the rest of the name
Each registry has its own checker with its rules and quirks: npm, 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.