npm-name
Check npm package name availability easily.
- Status
- Generally available
- Last checked
- Checked · Oct 16, 2026
- License
- Open source
- Pricing
- Free tier · from $0
What it is
npm-name is a tool that allows developers to quickly check if a desired package name is available on the npm registry, streamlining the process of publishing new packages without naming conflicts.
npm-name offers a simple, command-line based solution for checking npm package name availability, making it an essential tool for developers who prefer quick and easy integration into their workflows.
When it fits — and when it doesn’t
A good fit for
Developers who frequently publish packages and need quick name availability checks.
Teams working on multiple npm packages that require consistent naming strategies.
Look elsewhere if
Projects requiring real-time package name updates from the npm registry.
Users looking for a web-based interface to check package names.
Known weaknesses
Each one links to the public issue, changelog or docs page it came from, where we have one.
- 01
Limited functionality beyond name checking
npm-name is narrowly focused on package name availability, lacking advanced features like name suggestion or related package discovery.
- 02
No real-time updates from npm registry
The tool relies on the last known state of the npm registry which may not be up-to-date if there are recent changes in package availability.
- 03
Doesn't handle rate limiting or API errors gracefully
If the npm registry is down or rate-limited, npm-name does not provide fallbacks or retries, leading to potential false negatives on name availability.
What it does well
Quickly checks if a package name is available on npm.
Integrates easily into local development environments and scripts.
Simple command-line interface for ease of use.
Pricing
- Free tier
- YesOpen source — free to use
- Paid from
- $0
- Model
- Flat rate
- Enterprise plan
- No
Pricing not independently confirmed — check the vendor’s page.
Performance benchmarks
How Fast Is It?
Set up npm-name
Setup steps, common gotchas and what to check after 30 days.