Verified history
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean npm has never changed. Undated values are kept in the current baseline below instead of being presented as history.
Current monitored baseline
HyperObserve currently monitors 3 scoped observations for npm. The baseline covers experimental crawler velocity, token and scope counts, private package eligibility. Each value retains its plan, product, endpoint, region, account, or runtime qualifier so a future change can be compared against the correct scope.
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| experimental crawler velocitynpm directs full-dataset consumers to registry replication instead of high-velocity website crawling. | 1 request per second or less | Experimental website crawlers | npmAug 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 token | Granular access tokens | npmAug 22, 2026 |
| private package eligibilityPrivate organization packages require team access and a paid organization. | Paid user or organization account; packages must be scoped | Private packages | npmAug 22, 2026 |
Tracked constraints and impact
Registry crawling, granular token scope, and private package access constraints. A change is recorded only when it alters a constraint developers can act on, such as capacity planning, request shaping, model selection, deployment configuration, storage design, retry behavior, or account budgeting.
npm Website Crawler Rate Limit
npm Website Crawler Rate Limit, verified against npm's official documentation with scope, implementation impact, caveats, and a direct check.
npm Granular Access Token Limits
npm Granular Access Token Limits, verified against npm's official documentation with scope, implementation impact, caveats, and a direct check.
npm Private Package Requirements
npm Private Package Requirements, verified against npm's official documentation with scope, implementation impact, caveats, and a direct check.
How a change is verified
- Compare the current first-party statement with the previously stored observation, including the exact plan, model, runtime, endpoint, region, and account scope.
- Separate a true product change from documentation clarification, temporary capacity, configurable account state, or a limit that applies to a different execution path.
- Preserve the old and new values, official source, effective date when disclosed, detection date, and practical impact. If those elements cannot be supported, no historical event is published.
Official sources monitored
These first-party documents support the current npm baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
Website crawler velocity and registry replication guidance
Granular token, organization, package, and scope counts
Paid account, scoping, and visibility requirements