npm Package Name Checker – Online See If Slug Is Taken

Simply type the desired package name into the search box above and click "Check". Our tool queries the official npm registry API in real-time to determine if the name is already taken or available for use. You'll get instant feedback along with details about the existing package if the name is occupied.

NPM package names must follow these rules: (1) All lowercase letters — no uppercase allowed for new packages. (2) Maximum 214 characters total. (3) Cannot start with a dot (.) or underscore (_). (4) Can contain hyphens (-) and digits. (5) For scoped packages, use the @scope/package-name format. (6) Avoid names that are too similar to popular existing packages to prevent confusion.

Don't worry! You have several options: (a) Add a prefix like node- or npm-. (b) Add a descriptive suffix like -js, -lib, -util, or -core. (c) Use a scoped package under your npm username or organization: @yourname/package-name. (d) Try synonyms or alternative spellings that convey the same meaning. (e) Check if the existing package is abandoned or deprecated — sometimes owners transfer names.

A scoped package uses the format @scope/package-name, where "scope" is typically your npm username or organization name. Scoped packages are automatically namespaced, meaning @jane/my-lib and @john/my-lib can coexist without conflict. Scoped packages are private by default (if you have a paid npm plan) or can be published publicly. They're a great way to secure a name that might otherwise be taken in the global namespace.

As of 2024, the npm registry hosts over 2 million packages, making it the largest software registry in the world. With millions of developers publishing daily, popular and short package names get taken quickly. That's why it's essential to check availability early in your development process using tools like this NPM Package Name Checker.

npm does not officially support name reservation without publishing. However, you can publish a minimal placeholder package to claim the name. Some developers publish an empty or "coming soon" package. Be aware that npm has policies against squatting — deliberately registering names you don't intend to use may result in the package being transferred if someone files a dispute. The best practice is to publish your package when it's ready for use.

Yes, this tool is completely free and queries the official npm registry API directly, ensuring 100% accuracy. There are no rate limits for casual use. The results reflect the real-time state of the npm registry. We also provide additional information about existing packages — such as description, version, author, and license — so you can make informed decisions about naming your project.