Skip to content
npm Docs
npmjs.comStatusSupport
About npm
Getting started
Packages and modules
Introduction to packages and modules
Contributing packages to the registry
Creating a package.json file
Creating Node.js modules
About package README files
Creating and publishing unscoped public packages
Creating and publishing scoped public packages
Creating and publishing private packages
Package name guidelines
Specifying dependencies and devDependencies in a package.json file
About semantic versioning
Adding dist-tags to packages
Updating and managing your published packages
Getting packages from the registry
Securing your code
Integrations
Organizations
Policies
Threats and Mitigations
npm CLI

Package name guidelines

When choosing a name for your package, choose a name that

  • is unique
  • is descriptive
  • meets npm policy guidelines. For example, do not give your package an offensive name, and do not use someone else's trademarked name or violate the npm trademark policy.

Additionally, when choosing a name for an unscoped package, also choose a name that

  • is not already owned by someone else
  • is not spelled in a similar way to another package name
  • will not confuse others about authorship
Edit this page on GitHub