This article helps you resolve common installation problems with the Vibgrate CLI. It is for developers setting up the vg binary for the first time or on a new machine.
Try it without installing
If you only want to run a scan once, you do not need a global install:
npx @vibgrate/cli scan
This is also a quick way to confirm the package resolves and runs before committing to an install.
The vg command is not found
If your shell cannot find vg after installing, the most common causes are:
- The install location is not on your
PATH. Open a new terminal so PATH changes take effect. - The install did not complete. Re-run your package manager's install for
@vibgrate/cli. - You are in a different shell or container than where you installed.
As a fallback, the no-install form above always works if the package can be fetched.
Confirm the version
Check which version you are running:
vg --version
If it is older than expected, update:
vg update
Restricted networks
If the install fails to download, your network may require a proxy. The CLI honors your shell's standard HTTPS proxy settings; see the proxy and offline configuration article. For machines that should never reach the network, install where egress is allowed, then run scans with vg scan --offline.
Verifying a working install
Run a scan in any project directory to confirm everything works end to end:
vg
A successful run prints a summary and a DriftScore. If the scan runs but finds nothing, see the troubleshooting article on no projects detected.
Related
- Getting Started
- The
vg updatecommand page - Proxy and offline configuration