Growing npm
npm search matches words, not reputation. Clear wording in your description, keywords and README is what gets a package found.
Basics
How many people use npm?
npm doesn't publish a user count. Its docs call it "the world's largest software registry."[1]
How do people find your npm package?
Through npm search, which matches words in your package's name, summary, documentation and tags. npm applies no subjective ranking, only a small push down for spammy or brand-new packages.
| Field | What it does |
|---|---|
| description | Shown in npm search |
| keywords | Listed in npm search |
| README | Its text is matched in search |
| Name | Leave out "js" and "node", npm advises |
New packages can take up to two weeks to appear in search, and deprecated ones don't appear. People can also sort by downloads, dependents or last published date.
Using the same name on GitHub or a website? Check it on GitHub and the .com too.[2, 3]
Advanced
How do you show where your npm package was built?
Publish with provenance, so anyone can check where and how the package was built. It needs npm CLI 9.5.0 or later, a cloud-hosted GitHub Actions or GitLab CI/CD runner, and a public repository field in package.json.[4]
Can you publish to npm without long-lived tokens?
Yes, with trusted publishing, which signs in from GitHub Actions, GitLab CI/CD or CircleCI. On GitHub and GitLab, npm adds provenance automatically for public repositories and packages.[5]
Can people fund your npm package?
Add a funding URL to package.json. The npm fund command lists those links for everything a project depends on.[3]
Which npm paid plans are worth it?
Public packages are free; pay only when your team needs private packages. The order is our view.
| Option | Cost | What it buys |
|---|---|---|
| Free organization | $0 | Unlimited public packages |
| Paid organization | $7 per member a month | Private packages for members |