A single DriftScore tells you where you are today; a trend tells you whether you are getting better or worse. Vibgrate Cloud builds trend views automatically from the scans you push. This guide explains how to feed it and read it.
Overview
Every scan you push to Vibgrate Cloud is recorded with its DriftScore and the findings behind it. The dashboard at dash.vibgrate.com plots those points over time per repository, so you can see drift accumulating or being paid down.
Prerequisites
- An authenticated CLI (
vg login) or a DSN for automated uploads. - At least a few pushed scans — a trend needs more than one data point.
Step-by-step
Push results regularly under a consistent repository name so the points line up into one series:
vg scan --push --repository-name org/my-service
The more often you push (for example on every merge to your main branch), the smoother and more useful the trend. For continuous history, automate the push in CI; see Push from CI Pipelines and Schedule Recurring Drift Reporting.
Reading the trend
- A rising DriftScore over time means upgrade drift is being addressed.
- A falling score means drift is accumulating faster than it is paid down.
- Sudden steps usually map to a dependency bump or a large merge.
For what the number itself means, see the DriftScore help and Understand Drift Over Time.
Keeping history clean
Use the same --repository-name for every upload from a repo. A changing name fragments the trend. See Connect a Repository to Vibgrate Cloud.
Related
Set Up a Portfolio View to see trends across many repos at once, and Build Team Dashboards.