Private NPM Registry
A fully-compatible private NPM registry that works with npm, yarn, and pnpm. Publish scoped packages, lock down access with tokens, and serve private dependencies from your own channel. From £10/user/month.
Install private packages with the same tools your team already uses. No changes to your workflow.
Publish and install scoped packages like @myorg/my-package from your private registry. Configure a single scope to route to RepoForge and leave the rest pointing to the public registry — no disruption to existing workflows.
Works with npm, yarn (v1, v2, berry), and pnpm without any custom plugins. Add a single line to .npmrc or .yarnrc.yml and your team is installing from your private registry immediately.
Create fine-grained access tokens scoped to individual registries or your entire account. Grant read-only tokens to deployment environments and write tokens to your CI/CD system. Rotate without downtime.
Mirror public npm packages through your private registry so that a single .npmrc entry covers both private and public dependencies. Reduces registry calls and makes installs faster in restricted network environments.
Integrates with GitHub Actions, GitLab CI/CD, and any other CI system that supports .npmrc configuration. Store your access token as a secret and publish a new package version on every tagged release with no extra tooling.
Control who can publish, who can install, and which packages they can access. Set organisation-wide defaults and override per-user or per-token. Audit logs show every publish and install across your team.
Also available on RepoForge.io
Per user, per month. No bandwidth caps. No surprise invoices.
Need a custom plan? Contact us
Set up your private NPM registry in five minutes. Free tier available forever. No credit card required.
No credit card · Free tier forever · Up to 80% cheaper than Cloudsmith