starter.wikiSearch⌘K

JavaScript package registry

npm

The default public registry and package distribution service for the JavaScript ecosystem.

Visit official site

Editorial verdict

Use npm for public JavaScript packages unless access control, artifact formats, procurement, or enterprise governance require a different registry.12

Best for

  • Public JavaScript and TypeScript packages
  • Libraries expected to install through the standard npm client ecosystem
  • Maintainers prepared to secure ownership and publishing provenance
12

Not ideal for

  • Private multi-format artifacts
  • Teams needing repository-scoped access inherited from GitHub
  • Organizations requiring enterprise artifact promotion and retention controls
12
Main trade-off

npm provides the broadest JavaScript distribution path while maintainers own package naming, provenance, account security, compatibility, and public release discipline.12

Product boundary

Whether a package should use npm's public JavaScript distribution route or a private, multi-format, or enterprise registry.

npm is a JavaScript package registry and package-management ecosystem, not a general artifact repository or release-governance system.12

For: JavaScript and TypeScript maintainers publishing reusable public packages

  • The package must remain private.
  • Artifacts span ecosystems beyond JavaScript.
  • Enterprise retention, promotion, or procurement controls are mandatory.

Why teams consider npm

  • Ecosystem defaultJavaScript tooling resolves public packages through npm-compatible workflows.12
  • Public reachPublished packages are directly available to the broad npm consumer ecosystem.12
  • Publishing controlsOfficial guidance covers access, provenance, and trusted publishing.12

Pricing

Public package distribution is available without a package-hosting fee; current paid organization or private-package options must be checked on npm pricing.2

Public package

Public npm publishing

Model maintainer access, provenance, support, and release operations rather than registry hosting cost.2

Primary cost boundary
Public publishing versus paid private or organization features2
Operational boundary
Maintainer security and release process remain publisher-owned2
Pricing checked View official pricing

npm vs alternatives

GitHub Packages

Choose when
Package access should follow GitHub repository or organization workflows.
Avoid when
The package needs the broadest public npm discovery path.
Compared with npm
Distribution and permissions become more GitHub-dependent.45

Cloudsmith

Choose when
A managed multi-format registry and policy layer is required.
Avoid when
Only straightforward public npm distribution is needed.
Compared with npm
Commercial storage, transfer, and governance replace the ecosystem default.67

JFrog Artifactory

Choose when
Enterprise artifact promotion, repository topology, and multiple package types justify the platform.
Avoid when
The team cannot support enterprise administration.
Compared with npm
Capability expands with a much larger operating and licensing surface.89

Resources and sources

Official product, policy, pricing, and maintenance

  • About public packages
    Open
  • npm pricing
    Open
  • Trusted publishing for npm packages
    Open

Related tasks

  1. 1
    About public packages

    npm · Accessed Official

  2. 2
    npm pricing

    npm · Accessed Official

  3. 3
    Trusted publishing for npm packages

    npm · Accessed Official

  4. 4
    Introduction to GitHub Packages

    GitHub · Accessed Official

  5. 5
    Package access control and visibility

    GitHub · Accessed Official

  6. 6
    Cloudsmith supported formats

    Cloudsmith · Accessed Official

  7. 7
    Cloudsmith pricing

    Cloudsmith · Accessed Official

  8. 8
    Artifactory repository support for package clients

    JFrog · Accessed Official

  9. 9
    JFrog pricing

    JFrog · Accessed Official