Quick answer
npm documents private package eligibility as Paid user or organization account; packages must be scoped. Private organization packages require team access and a paid organization.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| 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 |
Why does this limit matter?
Publishing a scoped package without explicit public access can create an unexpected private-package billing requirement.
This value is scoped to Private packages; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Verify package scope, owner, access setting, team permissions, and billing plan before publish.
- 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
- Unscoped packages are always public and cannot be converted into private unscoped packages.
- 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