After installing the Vibgrate CLI, it is worth a quick check to confirm the vg command resolves and scanning works. This short guide shows how to verify your setup and fix the most common problems.
Check the version
The fastest check is the version flag:
vg --version
If this prints a version number, the binary is installed and on your PATH.
Run a quick scan
Confirm scanning works end to end by running a bare scan in any project directory. scan is the default subcommand, so this scans the current directory:
vg
A successful run prints findings and a DriftScore from 0 to 100.
Verify without installing
If you want to confirm the package itself runs without a global install, use the no-install form:
npx @vibgrate/cli scan
Common issues
vg: command not found— open a new terminal so PATH updates take effect. If it persists, confirm your package manager's global bin directory is on PATH, or run vianpx vg.- Wrong version active — you may have both a global and a project-local install; check which one resolves first on your PATH.
- Scan finds nothing — run from the directory containing your project's manifest and lockfile.
Keep it current
Once verified, keep the CLI up to date:
vg update
Related
See the install guides for macOS and Linux or Windows, and the first scan walkthrough to interpret your results.