Setting Baselines: How to Track Drift Over Time, Not Just Today

Snapshots vs. Trends

Running vibgrate scan gives you a snapshot — your drift score right now, your findings today, your priority actions for this moment. Snapshots are useful, but they do not answer the most important question: is our drift getting better or worse?

To answer that, you need a baseline — a saved reference point that future scans can compare against.

Creating Your First Baseline

The vibgrate baseline command runs a full scan and saves the result as your reference point:

vibgrate baseline

This writes the complete scan artifact to .vibgrate/baseline.json. Think of it as a bookmark in time: this was our drift posture on this date, and every future scan can measure delta against it.

Comparing Against a Baseline

Once you have a baseline, pass it to subsequent scans:

vibgrate scan --baseline .vibgrate/baseline.json

The report now includes a delta section showing:

• Score change (e.g., "Score improved from 48 → 56 (+8)")
• New findings that did not exist in the baseline
• Resolved findings that have been addressed
• Component-level changes (runtime improved, dependencies worsened, etc.)

This delta view transforms Vibgrate from a diagnostic tool into a tracking tool. You can see the direct impact of every upgrade you apply.

The Recommended Workflow

Here is how teams typically use baselines:

1. Baseline on main

Create your initial baseline on your main branch, right after a clean build:

git checkout main
vibgrate baseline
git add .vibgrate/baseline.json
git commit -m "chore: establish drift baseline"

2. Scan in CI with comparison

In your CI pipeline, every PR is scanned against the baseline:

vibgrate scan --baseline .vibgrate/baseline.json

This tells you whether the PR improves, worsens, or has no effect on drift.

3. Refresh after planned upgrades

When you complete a batch of upgrades (a runtime bump, a framework migration, a dependency cleanup sprint), create a new baseline:

vibgrate baseline
git add .vibgrate/baseline.json
git commit -m "chore: refresh drift baseline after Q1 upgrades"

This resets the reference point so future comparisons are relative to your new posture.

Why Baselines Matter

Without a baseline, drift is invisible between scans. A team might run Vibgrate once, see a score of 45, do some upgrades, re-scan and see 52, but not know whether those 7 points came from the upgrades they did or from changes in the ecosystem (new versions released, EOL dates approaching).

A baseline isolates your actions from ecosystem changes. The delta tells you exactly what your team accomplished — and what the ecosystem is asking of you.

The Vibgrate Code Intelligence Engine is built around this principle: drift is a continuous signal, not a one-time measurement. Baselines are the foundation for turning that signal into actionable intelligence.

Start tracking your drift trend. Sign up at dash.vibgrate.com to set your baseline, track progress over time, and see drift trends across every project in your portfolio.