Secure
Store and manage dependencies for dev and CI workflows without exposing internal packages to the public registry.
An npm-compatible registry for development, automated tests, and CI—private packages and granular access with minimal setup. Keep installs close to your editors, test suites, and pipelines as you iterate.
VSR fits best where you want a focused registry in the loop: local dev, shared team sandboxes, test fixtures, and CI—so private packages stay handy from first commit through green builds.
Store and manage dependencies for dev and CI workflows without exposing internal packages to the public registry.
Decide who can publish, read, or update packages—useful for team sandboxes, CI bots, and licensed or proprietary artifacts.
Run beside your laptop or in CI: private packages, scoped installs, and reproducible pipelines with a small footprint.
Fewer surprises in pipelines when installs are not pinned to a flaky or changing public mirror for every run.
Pin versions across dev machines, test jobs, and CI so everyone resolves the same tarballs before code ships.
Caches and proximity matter most in tight dev/CI loops—faster installs when your registry sits next to your runners instead of across the internet.
Granular access tokens (GAT) offer the ability to provide precise control over who can interact with what and how.
Read-only tokens offer secure, controlled, and revokable access to proprietary packages, enabling businesses to manage third-party access while protecting intellectual property.
Create read-only and read & write maintainer tokens to provide comprehensive and flexible access control for managing packages within an organization, allowing for collaborative and secure package management.
Capabilities both VSR and Verdaccio support today—useful baseline for npm-style workflows. VSR is especially at home in development, testing, and CI.
VSR is released under the Functional Source License (FSL) - a Fair Source license. You get source access and broad use rights while the license protects sustainable product development; under FSL, each version typically becomes permissive open source (Apache 2.0 or MIT) after two years. Our managed registry, mirror, and related hosted services are primarily closed source and sold separately - see our open source page for the libraries and tools we publish under permissive licenses.