Quick answer
npm documents experimental crawler velocity as 1 request per second or less. npm directs full-dataset consumers to registry replication instead of high-velocity website crawling.
Verified Aug 22, 2026Official source
Current limits
| 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 |
Why does this limit matter?
Scraping the website is slower and more likely to be blocked than using the supported replication feed.
This value is scoped to Experimental website crawlers; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Identify whether the task needs website pages, registry metadata, or full replication.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- This policy is for crawling npm's website, not a universal npm registry API rate.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related