N

Package Managers

npm: JavaScript Package Manager and Registry

npmjs.com · checked 27 Sept 2026

npm manages JavaScript packages, dependencies, workspaces, and publishing through its command-line tools and registry.

How it plugs in

—Public API
NoOpen source
YesFree tier

Signal on Package Managers7.5#1 of 93

GitHub operates npm, a registry and package manager for JavaScript. It installs and publishes code, resolves dependencies, supports lockfiles and workspaces, and offers private packages and offline installation. Node.js installers or version managers provide access on macOS, Windows, Linux, and other systems. Public packages are available on the free plan, while private publishing is paid.

npm home page

Review

In a line

For JavaScript projects, npm combines package management with a public registry. Its command-line tools connect developers to shared JavaScript code.

What it does

Packages can be selected by name and version, tag, URL, or Git URL. npm resolves required dependencies, supports lockfiles, and provides workspaces for projects containing multiple packages.

It also handles package publishing. More than two million packages are listed in the community’s free registry.

How it connects

npm accepts package.json folders, compressed tar files, URLs, and Git sources. Private registry sign-in, offline installation, and package access controls are supported.

Its documentation explains private-package use in CI/CD workflows, Docker, and related setups. Node.js installers or version managers support npm on macOS, Windows, Linux, and other operating systems. See JavaScript package managers for related tools.

Good fit

npm suits JavaScript developers who need a shared place to find, install, or publish code. It can also fit individuals and organizations that need private packages, workspace support, and controls for members, teams, roles, and package access.

The free plan targets public package authors. Individual creators can use Pro, while Teams is designed for teams and organizations.

Watch for

Private publishing is not included in the free plan. Check whether you need an individual or team plan, since their permission systems differ.

Submitting credit-card information starts paid billing, and the first month is charged immediately. Every plan includes basic support.

Pricing

At $0 per month, Free provides public package publishing and use, public registry access, unlimited public packages, and automatic security warnings.

Private publishing is available through the $7-per-month paid user account. Pro is also $7 monthly for an individual creator and adds unlimited private packages with package-based permissions.

Teams charges $7 per user each month for teams and organizations, with unlimited private packages and team-based permissions. Free, Pro, and Teams all include unlimited public packages and automatic security warnings.

Verdict

Choose npm if your work centers on JavaScript and you want dependency handling, a large public registry, or private package publishing. Its workspace, lockfile, offline, and access-management features cover common project and organization needs.

Look elsewhere if JavaScript is outside your work or if the available private-package plans and permission models do not suit your budget or team structure. You can compare it with other package managers.

Our take

npm is a practical choice for JavaScript projects needing a familiar registry and dependency manager. Public packages are covered at no cost, while individual and team options add private publishing from $7 monthly. Lockfiles, workspaces, offline installs, private registry access, and CI/CD or Docker documentation broaden its use. Confirm that JavaScript is your target and that the paid plan’s billing and permission model fit your organization.

  • Free registry access and unlimited public packages
  • Resolves dependencies and supports lockfiles
  • Supports workspaces and offline installation
  • Runs on macOS, Windows, Linux, and other Node.js systems
  • Private packages available from $7 per month
  • Private publishing requires a paid plan
  • Paid billing starts immediately after card submission
  • Pro and Teams use different permission models
  • Focused on JavaScript package sharing
  • Pick it ifJavaScript developers managing shared dependencies; Creators or teams publishing private packages; Projects needing workspaces and lockfiles
  • Skip it ifYou are not building or sharing JavaScript code; You need private packages without a paid plan; The listed individual or team permissions do not fit

Pricing

Free covers public packages. Billing is monthly, with the first paid month charged when a card is submitted.

  • Freebilled monthly · Public package publishing and use · Public registry accessFree
  • Paid user accountbilled monthly · Install and publish private packages$7/mo
  • Pro$7 per month$7/mo
  • Teams$7 per user per month$7/mo

As npmjs.com lists them, checked 27 Sept 2026.

Questions

Does npm have a free option?

Yes. The npm Registry and CLI are offered to the community for free, and Free includes unlimited public packages. Private publishing requires a paid plan.

What is the price for npm private packages?

The paid user account is $7 per month. Pro is $7 monthly for an individual creator, and Teams is $7 per user each month.

Which operating systems can run npm?

Node.js installers or version managers make npm available on macOS, Windows, Linux, and other operating systems.

Is offline package installation available in npm?

Yes. npm supports installing packages without an online connection.

Are workspaces and lockfiles available?

Yes. npm provides both features and resolves project dependencies.

Can organizations manage access to private packages?

Yes. npm supports organizations, members, teams, roles, permissions, and package access management. Pro uses package-based permissions; Teams uses team-based permissions.

Are CI/CD and Docker covered?

npm documentation explains private-package use in CI/CD workflows and Docker environments.