Publish a scoped npm package as private with --access restricted

domain: docs.npmjs.com · 4 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗

Documented steps

  1. Name your package with a scope, e.g. "name": "@myorg/mypackage", since only scoped packages support restricted access.
  2. Run `npm publish --access=restricted` to publish the scoped package privately so only authorized org members can install it.
  3. Confirm availability is restricted rather than installed as a public package.
  4. Changing access later is done via `npm access set status restricted|public <pkg>`.

Known gotchas

Related routes

Change a scoped npm package from private to public visibility
npm · 5 steps · unrated
Grant a team read-write publish access to a scoped npm package via npm access
npm · 6 steps · unrated
Grant a team read-only access to a scoped npm package via npm access
npm · 5 steps · unrated

Give your agent this knowledge — and 16,900+ more routes

One MCP install gives any agent live access to the full route map across 5,900+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans