Getting started
You need the Veln CLI on a developer machine, an org license from the cloud console, and a project with real lockfiles (for example npm, pnpm, yarn, or Python lockfiles your stack already uses).
1. Install the CLI
Use the official installer for your OS — see the Veln Console Install page for copy-paste commands for macOS, Linux, and Windows. After install, confirm with veln version.
2. Activate
Create an org in the console (or accept an invite), then run veln activate. The CLI opens your browser to approve this machine and stores a device access token locally — no tokens to copy or paste into environment variables. Re-running veln activate later refreshes the token.
3. Run verify
From a project root, run veln verify -dir . (or your chosen directory). Read the result in the terminal — that is the primary enforcement surface. Use --json when you need machine-readable output for scripts.
4. Optional: gate
For automatic checks on registry traffic, configure and run Gate so dependencies are evaluated as your package manager fetches them — still with outcomes visible from the CLI and tooling you wire up.