Open source project name generator
For the library, CLI or framework you’re about to publish. Names are checked against npm, GitHub and the domains you’d host docs on, so the name you pick is the one people install.
Naming an open source project
- Why does the npm name matter so much?
- Unscoped npm package names are global and first-come. If yours is taken you’re left with a scope (@you/name) or a variant nobody remembers. Starting with a name that’s free on npm keeps the install command short.
- Can npm still reject a name that looks free?
- Yes. npm blocks some new names that are too similar to existing packages — for example, ones that differ only by punctuation. A free name here is a good sign, but npm has the final say when you publish.
- Should the GitHub org match?
- Ideally — people guess github.com/name before they search. Every name is looked up on GitHub (users and orgs), npm and the domains before it’s dealt, and “Full check” shows each result.
- Do open source projects need a trademark?
- Many never register one, but you still don’t want to collide with someone else’s. Larger projects often register a mark later to stop confusing forks and products, and a clear name now keeps that option open.