Understand Your DriftScore

The DriftScore is Vibgrate's headline metric: a single 0 to 100 number that summarizes how far your project has drifted from current, supported dependency versions. This tutorial explains what it represents and how to use it without getting lost in the details of individual findings.

Prerequisites

• Vibgrate CLI installed
• A project you can scan

Steps

1. Run a scan to get a score

vg

The scan prints a results table and a DriftScore for the repository.

2. What the DriftScore measures

The DriftScore reflects upgrade drift detected across your dependencies and ecosystems. It rolls many individual findings into one comparable number so you can judge a repository at a glance rather than reading every line.

3. Read the score as risk

The score runs from 0 to 100, where lower means less drift and therefore lower upgrade risk. Use it as a relative signal: compare repositories, or compare the same repository before and after an upgrade push.

4. Connect findings to the score

The findings in the scan table are the inputs that contribute to the score. To bring the number down, work through the highest-impact findings first, then re-scan to confirm the score moved.

vg

5. Track the score over time

To measure progress, capture a baseline and compare future scans against it.

vg baseline

Verification

Each scan prints a DriftScore. After remediating findings and re-scanning, a lower score confirms reduced drift. A baseline lets you confirm the direction of change between scans.

Next Steps

• Want to act on the score in CI? Set a drift budget gate.
• Comparing scans over time? Read the baseline tutorial.
• Need the score in machine-readable form? Choose an output format.