View Drift on the Vibgrate Cloud Dashboard

Once a scan is in Vibgrate Cloud, the dashboard becomes the team's source of truth for drift. This tutorial walks through getting a scan up there and then reading it: where to find your DriftScore, what the risk levels mean, and how to see which packages and signals are driving drift.

Prerequisites

• The Vibgrate CLI installed (npm i -g @vibgrate/cli)
• A Vibgrate Cloud workspace

Steps

1. Sign in and scan

vg login

Then run the default scan from your project root.

vg

2. Push the scan

vg push

This uploads the latest results to Vibgrate Cloud. You can also combine the two steps with vg scan --push.

3. Open the dashboard

Go to dash.vibgrate.com and sign in. Select the workspace and repository you just pushed to.

4. Read your DriftScore

The dashboard shows your DriftScore (0-100) front and center, along with the risk level it maps to. A higher score means more upgrade drift accumulated against your lockfile and platform signals.

5. Drill into drift contributors

Expand the repository view to see the packages and signals contributing most to your drift. This is the same data your local vg report produces, presented for the whole team with history.

Verification

The DriftScore shown on the dashboard should match the score your CLI reported for the same scan. If you do not see the repository, confirm the push exited 0 and that you are viewing the correct workspace.

Next Steps

• Watch the score move over time: "Track Drift Trends Over Time in Vibgrate Cloud".
• Build an organization-wide view: "Set Up a Portfolio View Across Repositories".