Run Your First Vibgrate Scan on the Current Directory

Your first Vibgrate scan tells you, in one number, how far your project's dependencies have drifted from current, supported versions. The default subcommand is scan, so you do not even type the word: a bare vg scans the current directory. There is no need to pass a trailing path argument.

Prerequisites

• Vibgrate CLI installed (or use the npx form)
• A project with dependency manifests and lockfiles

Steps

1. Open your project

Change into the repository you want to scan so the current directory is the project root.

2. Run a bare scan

vg

Because scan is the default subcommand, this scans the current directory and prints a results table.

3. See what was analyzed

Vibgrate reads your manifests and lockfiles to analyze upgrade drift across ~19 ecosystems, including Node.js, .NET, Python, Java, Go, Rust, PHP, and Ruby. The findings in the table represent dependencies that have drifted.

4. Find the DriftScore

The headline output is the DriftScore, a 0 to 100 metric where a lower number means less drift. Treat it as the single summary of the repository's upgrade health.

5. Re-run after a change

After updating a dependency, scan again to see the DriftScore move.

vg

Verification

A successful scan prints a results table and a DriftScore. With no failure gate configured, the command exits 0. If nothing is detected, confirm you are in a directory that contains dependency manifests.

Next Steps

• Want to understand the number? Read the DriftScore explainer tutorial.
• Need machine-readable output? Choose an output format.
• Track changes over time? Create a baseline with vg baseline.