Can this replace a private npm org?
Yes. PackagePass is built for private package distribution where access needs to follow customers, projects, users, and CI workflows.
private npm registry
Generic registries make private package access feel like org membership. PackagePass lets teams publish private packages and grant install access by user, project, customer, or CI job.
Product demo
Create a scoped private package repository.
Grant install access to a customer, teammate, agent, or CI token.
Install with npm, pnpm, Yarn, or Bun using the same package name.
Proof point
npm-compatible installs with first-party grants, tokens, preview packages, and audit events.
Simple pricing
Free for early setup. Team plans add higher limits, longer audit retention, and production package workflows.
@acme:registry=https://registry.packagepass.dev/npm/
//registry.packagepass.dev/npm/:_authToken=${PACKAGEPASS_INSTALL_TOKEN}
always-auth=trueFAQ
Yes. PackagePass is built for private package distribution where access needs to follow customers, projects, users, and CI workflows.
No. Packages install through standard npm-compatible clients including npm, pnpm, Yarn, and Bun.