Skip to main content

Install the Vibgrate CLI with pnpm, yarn, or bun

Install the Vibgrate CLI globally with pnpm, yarn, or bun, then verify the vg binary and run a first scan. The CLI behaves identically across package managers.

Difficulty
Beginner
Duration
10 minutes
Steps
5

The Vibgrate CLI is published to npm as @vibgrate/cli, so you can install it with whichever package manager your team standardizes on. This tutorial covers global installs with pnpm, yarn, and bun, then verifies the vg binary works the same way in each.

Prerequisites

  • One of pnpm, yarn, or bun installed
  • Node.js 18+ for pnpm and yarn
  • A project to scan

Steps

1. Pick your package manager

Use the manager your team already relies on so the binary lands in the expected global location.

2. Install with pnpm

pnpm add -g @vibgrate/cli

3. Install with yarn

yarn global add @vibgrate/cli

4. Install with bun

bun add -g @vibgrate/cli

5. Verify and scan

No matter which manager you used, the binary is vg. Confirm it resolves and then run a scan from your project root.

vg --version

The default subcommand is scan, so a bare vg scans the current directory.

vg

Vibgrate prints a results table and a DriftScore from 0 to 100 that summarizes your dependency drift.

Verification

vg --version prints a version number when the global install succeeded. A bare vg produces a results table and DriftScore. If vg is not found, confirm your package manager's global bin directory is on your PATH.

Next Steps

  • Prefer not to install at all? Use the npx no-install workflow.
  • Want isolation from the host? Run the CLI via Docker.
  • Ready to add config? Initialize the project with vg init.

Prerequisites

  • pnpm, yarn, or bun installed
  • Node.js 18+ for pnpm and yarn

Steps

  • 1
    Pick your package manager
  • 2
    Install with pnpm
  • 3
    Install with yarn
  • 4
    Install with bun
  • 5
    Verify and scan

Category

Vibgrate