Installation
Install and configure the VertaaUX CLI on your system
Installation
Install the VertaaUX CLI using your preferred method.
Installation Methods
Install globally for persistent access:
Verify installation:
@vertaaux/cli v1.0.0
Project-local Installation
For CI/CD or team consistency, install as a dev dependency:
npm install --save-dev @vertaaux/cliThen run via npx or npm scripts.
Run directly without installing:
This downloads and runs the latest version each time. Best for one-off usage or trying out the CLI.
npx adds a small startup delay while it checks for updates. For frequent use, global installation is faster.
Download pre-built binaries from GitHub Releases.
macOS (Apple Silicon):
curl -L https://github.com/vertaaux/cli/releases/latest/download/vertaa-darwin-arm64 -o vertaa
chmod +x vertaa
sudo mv vertaa /usr/local/bin/macOS (Intel):
curl -L https://github.com/vertaaux/cli/releases/latest/download/vertaa-darwin-x64 -o vertaa
chmod +x vertaa
sudo mv vertaa /usr/local/bin/Linux (x64):
curl -L https://github.com/vertaaux/cli/releases/latest/download/vertaa-linux-x64 -o vertaa
chmod +x vertaa
sudo mv vertaa /usr/local/bin/Windows:
Download vertaa-win-x64.exe from releases and add to your PATH.
System Requirements
- Node.js 18+ (for npm/npx installation)
- Operating Systems: macOS, Linux, Windows
Authentication
After installation, authenticate with your VertaaUX account.
Option 1: Interactive Login
Enter your API key when prompted. Get your key from the VertaaUX Dashboard.
Credentials are stored in ~/.vertaaux/config.json.
Option 2: Environment Variable
Set VERTAA_API_KEY in your environment:
export VERTAA_API_KEY=vx_live_your_key_hereAdd to ~/.bashrc or ~/.zshrc for persistence.
set VERTAA_API_KEY=vx_live_your_key_hereFor persistence, use System Properties > Environment Variables.
$env:VERTAA_API_KEY = "vx_live_your_key_here"CI/CD Environments
In CI/CD, always use the environment variable method. Store your API key in your CI provider's secrets management (GitHub Secrets, GitLab CI Variables, etc.).
Option 3: Configuration File
Add your API key to .vertaaux.yml:
apiKey: vx_live_your_key_here # Not recommended - use env var insteadSecurity Warning
Avoid committing API keys to version control. Use environment variables or your CI provider's secrets management.
Verify Setup
Check that everything is working:
Authenticated as: your-email@example.com Plan: Pro Credits remaining: 950/1000
If you see your account details, you're ready to run audits.
Proxy Configuration
If you're behind a corporate proxy:
export HTTPS_PROXY=http://proxy.example.com:8080
export HTTP_PROXY=http://proxy.example.com:8080
vertaa audit -u https://example.comUpdating
npm
Binary
Download the latest binary from GitHub Releases and replace the existing binary.
Uninstalling
npm
Binary
Remove the binary from your PATH:
sudo rm /usr/local/bin/vertaaOptionally, remove stored credentials:
rm -rf ~/.vertaauxTroubleshooting
"command not found: vertaa"
Cause: The CLI is not in your PATH.
Solutions:
- For npm global installs, ensure npm's global bin directory is in your PATH:
npm config get prefix # Shows npm prefix export PATH="$(npm config get prefix)/bin:$PATH" - For binary installs, verify the binary location is in your PATH.
"Unauthorized" or "Invalid API key"
Cause: Missing or invalid authentication.
Solutions:
- Run
vertaa loginand re-enter your API key - Verify your API key at dashboard/api-keys
- Check that
VERTAA_API_KEYenvironment variable is set correctly
"EACCES: permission denied"
Cause: npm lacks permissions to write to global directory.
Solutions:
- Use a Node version manager (nvm, fnm) which doesn't require sudo
- Or fix npm permissions: npm docs
Related
- Quickstart - Run your first audit
- Configuration - Configure defaults with .vertaaux.yml
- API Authentication - How authentication works
Was this page helpful?