npm

npm is a package registry and command-line interface for JavaScript developers who need to publish or install shared code. It is strongest for public distribution and established JavaScript workflows; private publishing comes with a recurring fee.

Overview

GitHub operates npm’s Registry and CLI. The Registry contains more than two million packages and is relied on by more than 17 million developers worldwide, giving JavaScript projects a large pool of reusable code. The free tier supports unlimited public packages, making npm a practical choice for open distribution. Its JavaScript focus makes it less suited to teams seeking a general-purpose package ecosystem.

npm supports Linux, macOS and Windows, with other operating systems supported through Node.js installers or version managers. Dependency resolution, lockfiles and workspaces cover common project needs, while offline installation and private registry authentication extend its use beyond public packages.

For broader comparisons, browse JavaScript Package Managers, Package Managers or Package Registries.

Key features

Package distribution and project workflows

npm accepts package.json folders, gzipped tarballs, URLs, name-and-version and name-and-tag references, and Git URLs. That range is useful when a project’s dependencies come from more than one source. Lockfile and workspace support help manage dependency versions and related packages; offline installation is a further advantage when network access is unavailable.

Access and security controls

Automatic security warnings are included across Free, Pro and Teams, and npm documentation covers two-factor authentication for accounts, organizations, publishing and settings changes. Pro adds package-based permissions, while Teams provides team-based permissions and organization management for members, roles and package access. CI/CD and Docker workflows for private packages are also covered in npm documentation.

Pricing

The Free plan costs nothing, billed monthly, and is aimed at public package authors. It includes unlimited public packages, public publishing and use, public registry access, automatic security warnings and basic support. It is a strong fit for open-source publishing, but does not include private publishing.

Paid user account costs $7 a month, billed monthly, for installing and publishing private packages. Pro costs $7 a month for individual creators and includes unlimited private packages and package-based permissions. These plans suit individuals who need private distribution; the paid user account description is narrower, while Pro explicitly adds permissions.

Teams costs $7 per user per month for teams and organizations, with unlimited private packages and team-based permissions. It is the relevant tier when access needs to be managed by team rather than package alone, but per-user billing makes costs rise with team size. All plans include unlimited public packages, automatic security warnings and basic support. Paid billing begins when card information is submitted, and the first month is charged immediately.

Platforms

npm supports Linux, macOS and Windows. Other operating systems can use it through Node.js installers or version managers.

Who it's for

npm is a natural choice for JavaScript developers who want to consume dependencies, publish public packages or manage workspaces. Individual creators needing private packages can choose Pro; organizations that need team-based access controls are better matched to Teams. Developers working primarily in other language ecosystems should consider a more specialized alternative.

Pros and cons

• Pros: Unlimited public packages on the free plan make public publishing accessible without a package cap.
• Pros: Lockfiles, workspaces, dependency resolution and offline installation support varied project workflows.
• Pros: Pro and Teams both allow unlimited private packages, with distinct permission models for individual creators and organizations.
• Cons: Private publishing requires a paid plan, so the free tier does not cover private package distribution.
• Cons: Teams is priced per user, which can make it less attractive as an organization grows.

Alternatives

Choose uv instead if you want a free package manager for Python. Yarn is another free package manager with no paid plans stated. For Rust, Cargo is a free package manager and build tool; PHP developers may prefer Composer for dependency management. Gradle is a free open-source build system, while Pixi offers a free package-hosting option. Hex is another package registry with a free open-source plan. pnpm is also a free package manager.

For related tool categories, see Monorepo Management Tools.

Verdict

Choose npm for JavaScript projects that benefit from its large public Registry, broad package inputs and built-in dependency workflow. Its free public publishing is compelling, but anyone needing private packages must budget for a paid plan, and teams should account for per-user pricing.