▶ vg scan — first DriftScore across five stacks (docs)

[vibgrate-team]

▶ Run the interactive CLI simulator →
_{Real recorded runs. First DriftScore on the stacks the Scan docs already replay. No signup.}

Look how clean a first DriftScore is

One local command. Ranked priorities. A bare scan reports; it does not fail the process. A budget is the later, honest gate.

vg

Then the same tree with a budget (the recorded gate uses 60):

vg scan --drift-budget 60

Same command on every recorded stack — the Example use cases on vg scan. The CLI home is vibgrate.com/cli.

Scan — score the codebase

Notice: scan defaults to the current directory; the report is a computed DriftScore plus findings. Without --drift-budget the process does not fail on a high score. The Java recording on the docs page is a passing budget. The honest failing gate lives on vibgrate.com/cli as node-turborepo/budget — watch the player for scores; do not paste numbers here.

New here? Getting started with Vibgrate CLI. Walkthrough: your first Vibgrate scan.

— Vibgrate maintainers