Use cases
vlt was created with the needs of open source maintainers and development teams in mind.
These are some primary use cases for choosing vlt.
-
Private registry for internal packages — Share private packages within your org, while keeping them out of the public npm registry.
-
High-availability for critical open-source packages and libraries used by thousands of developers.
-
Multi-registry workflows — Configure named registries in vlt to pull from npm, a private mirror, and an internal registry simultaneously, routing specific scopes (e.g.
@internal/) to the right source. -
Supply chain protection for your team vlt offers security scanning of dependencies — Run
vlt query ':malware'with our CLI to detect malware, vulnerabilities, and license issues in your dep graph via Socket integration, without leaving the CLI. -
Full transparency on dependencies inside package artifacts.
-
Monorepo package management — vlt’s workspace-aware client can install, query, and manage dependencies across a multi-package monorepo with a single tool, replacing fragmented workflows.