Vibgrate scans Rust crates and workspaces for upgrade drift as part of its multi-ecosystem support. This guide takes a Rust developer from install to first scan and baseline.
Prerequisites
- The Vibgrate CLI installed (or use
npx @vibgrate/cli scan) - A Rust project with
Cargo.tomlandCargo.lock
New to installing? See install the Vibgrate CLI on macOS and Linux or install on Windows.
Run your first scan
From the crate or workspace root, run the bare command to scan the current directory:
vg
Vibgrate reads Cargo.toml and Cargo.lock, analyzes the dependency graph, and prints a DriftScore from 0 to 100 plus the findings it detected. A higher score indicates more upgrade drift.
Initialize project config
Store Vibgrate settings in the repository:
vg init
This creates the .vibgrate directory and config file to commit.
Establish a baseline
Snapshot the current state so later scans report deltas:
vg baseline
Compare future scans against it:
vg scan --baseline .vibgrate/baseline.json
Output for pipelines
Produce structured output for CI:
vg scan --format sarif
Troubleshooting
- Workspace with many crates — run from the workspace root so the full member graph is analyzed.
- No lockfile — generate
Cargo.lockso Vibgrate can resolve exact versions.
Related
Read understanding your first DriftScore to interpret the result and drift baselines to add CI gates. You can also serve version-correct Rust crate docs to your AI assistant with Vibgrate AI Context via vg serve.