Track Your Drift Trend Across Releases

A single DriftScore tells you about today. A trend tells you whether you are winning. By baselining each release and comparing the next one against it, you build a clear picture of drift moving up or down over time.

Prerequisites

• Vibgrate CLI installed (npm i -g @vibgrate/cli)
• A release or tagging workflow

Steps

1. Baseline at the release point

When you cut a release, capture its drift state:

vg baseline

2. Archive the release baseline

Keep the per-release baseline by committing it under a release-specific path or tag so you can refer back to it later. The default snapshot lives at .vibgrate/baseline.json.

3. Scan the next release against it

At the next release, compare against the previous baseline to measure the change:

vg scan --baseline .vibgrate/baseline.json

4. Push results for trend tracking

For a visual trend across releases, send results to Vibgrate Cloud:

vg scan --push

The dashboard at dash.vibgrate.com charts DriftScore over time.

5. Verify the trend

Compare the delta from one release to the next. A shrinking delta and a falling DriftScore mean drift is improving.

Verification

With two or more release baselines, each vg scan --baseline comparison shows the direction of change. The Vibgrate Cloud trend line confirms the long-run picture.

Next Steps

• Add a drift budget so the trend cannot quietly reverse.
• Set per-team budgets to attribute the trend to specific owners.