Baseline
16 items tagged with "baseline"
Tutorials12
Initialize Vibgrate Config with vg init
Use vg init to create the .vibgrate directory and config file so your scans are repeatable and shareable across the team.
Create Your First Drift Baseline with vg baseline
Capture a point-in-time snapshot of your project's upgrade drift so future scans can be compared against a known-good reference.
Scan Against a Drift Baseline for Delta Comparison
Compare a fresh scan against a saved baseline with vg scan --baseline to see exactly how your upgrade drift changed since the snapshot.
Fail CI When New Drift Appears Against a Baseline
Wire vg scan --baseline into your pipeline so any new upgrade drift introduced by a change fails the build before it merges.
Track Your Drift Trend Across Releases
Baseline each release and compare scans against it to see whether your DriftScore is improving or degrading over the project's lifetime.
Baseline a Monorepo One Package at a Time
Create and scan per-package drift baselines in a monorepo so each workspace owns its own drift ceiling instead of one shared number.
Update and Refresh an Existing Drift Baseline
Re-run vg baseline to refresh your snapshot after intentional, reviewed changes so the baseline reflects the new accepted normal.
Initialize a Project With a Baseline Using vg init --baseline
Bootstrap Vibgrate and create an initial drift baseline in one step with vg init --baseline so new projects start with a reference snapshot.
Compare Two Drift Baselines to Measure Change
Pin a scan to an older baseline file while a newer one exists to measure exactly how much your upgrade drift moved between two points in time.
Prevent Drift Regressions on a Legacy Module
Pin a baseline to a legacy module and gate it so the old code can't get worse, even while you avoid a risky full rewrite.
Interpret Baseline Diff Output
Learn how to read the delta from vg scan --baseline so you can tell new drift apart from carried-over drift and act on the right items.
Commit the Drift Baseline to Your Repository
Check your baseline file into version control so every developer and CI run compares against the same shared drift reference.
FAQs4
How do I create a drift baseline?
Run vg baseline to perform a full scan and save the result to .vibgrate/baseline.json. This snapshot becomes your reference point for measuring whethe...
Should I add .vibgrate to .gitignore?
Add .vibgrate/scan_result.json to .gitignore (it changes on every scan). Keep .vibgrate/baseline.json in version control so CI can compare against it ...
How do I compare two scan results?
Use vg sbom delta --from old-scan.json --to new-scan.json to see dependencies added, removed, and changed between scans. For drift score comparison, u...
What is the baseline.json file for?
The .vibgrate/baseline.json file is a snapshot of your drift score at a point in time. It serves as a reference point for CI gates — you can fail buil...