What are npm's package naming rules?

A package name must be lowercase, URL-safe, 214 characters or fewer, may not start with a dot or underscore, and may not contain spaces or these characters: ~)(*!'. It can include hyphens, dots, digits and a leading scope. This tool only emits names that satisfy every rule.

What is a scoped package?

A scoped name is prefixed with @scope/, for example @acme/parser. Scopes group related packages under an organisation or user and let you publish a name that is already taken in the global unscoped namespace. The tool can generate either form.

Are the names available to publish?

Not necessarily. The unscoped npm namespace is shared globally, so a generated name may already be taken. The tool produces valid names but cannot check the registry — run npm view or check npmjs.com before publishing.

Why must npm names be lowercase?

Older mixed-case package names exist, but npm now requires new names to be lowercase to avoid case-collision problems across case-insensitive file systems and URLs. The generator always lowercases its output to comply.

Does the tool query npm or any server?

No. Every name is built locally in your browser with no network calls, so it works offline and nothing you generate is sent to npm or anywhere else.

npm Package Name Generator

Valid names for your next package

npm publish will reject a name that breaks the registry’s rules, which is an annoying way to discover a typo. The npm Package Name Generator produces names that already satisfy every constraint — lowercase, URL-safe, within the length limit — in both unscoped and scoped forms, so you can drop one straight into your package.json.

How it works

npm’s validation requires a name that is lowercase, 214 characters or fewer, URL-safe, not starting with a dot or underscore, and free of spaces and the forbidden characters ~)(*!'. The generator assembles words from curated lists, joins them with hyphens, lowercases everything, and strips any character outside the safe set. For a scoped package it prefixes a @scope/ segment, where the scope itself follows the same character rules.

Each candidate is then checked against the registry’s published validation logic — leading character, allowed characters, and length — before being shown, so every result would pass npm publish’s name check. Availability is a separate question the tool can’t answer, since the unscoped namespace is global.

Tips and example

Unscoped: color-utils, parse-config, tiny-router.
Scoped: @acme/color-utils — useful when the unscoped name is taken or you want to group org packages.
Prefer short, descriptive names; they’re easier to remember and search for on npmjs.com.
Always confirm availability with npm view <name> before publishing — a valid name is not a free name.
All names are synthetic suggestions; verify trademark and availability before real use.