Platform hub

npm limits

Registry crawling, granular token scope, and private package access constraints. Values below are scoped rather than flattened into one misleading platform-wide number.

Verified Aug 22, 2026Official docs
Quick answer:  npm has multiple independent constraints. Match the exact plan, model, runtime, invocation mode, or server configuration shown in each row.

Current documented limits

ConstraintCurrent valueScopeVerified source
experimental crawler velocitynpm directs full-dataset consumers to registry replication instead of high-velocity website crawling.1 request per second or lessExperimental website crawlersnpmAug 22, 2026
token and scope countsA token can select packages, scopes, or a combination within the documented count.1,000 tokens/account; 50 orgs and 50 packages/scopes per tokenGranular access tokensnpmAug 22, 2026
private package eligibilityPrivate organization packages require team access and a paid organization.Paid user or organization account; packages must be scopedPrivate packagesnpmAug 22, 2026

How to apply npm limits safely

The monitored baseline covers experimental crawler velocity, token and scope counts, private package eligibility. Treat these as separate constraints rather than one platform-wide capacity number: a workload can fit one row and still fail another because the plan, model, endpoint, runtime, region, invocation mode, or account scope differs.

  1. Match the production workload to the exact scope printed beside each value and confirm it in the active npm console, configuration, or response headers.
  2. Measure the serialized request, token volume, duration, concurrency, storage, or connection demand at realistic percentiles, then preserve headroom for bursts and retries.
  3. Check every adjacent layer—client, SDK, gateway, proxy, queue, database, and downstream service—for a smaller effective limit before changing architecture.

Specific limit pages

These pages exist because the constraint has a distinct implementation or troubleshooting intent. Closely related keyword variations stay consolidated.

Compare alternatives

Official sources

View npm change history