Local scans are great for the developer who ran them, but teams need a shared view. Vibgrate Cloud (the hosted dashboard at dash.vibgrate.com) collects scan results so everyone can see DriftScore, findings, and how they change over time. This guide explains how to get results there.
Overview
There are two ways to upload: scan and push in one step, or push artifacts from a scan you already ran. Both send results to your Vibgrate Cloud workspace, where they appear with their DriftScore and finding detail.
Prerequisites
- A Vibgrate Cloud workspace.
- The CLI authenticated to that workspace. The simplest path is browser login:
vg login
Step-by-step
Option 1 — scan and push together
The most common pattern is to scan and upload in a single command:
vg scan --push
This runs the scan and uploads the results when it finishes.
Option 2 — push an existing scan
If you have already scanned and want to upload those artifacts:
vg push
Authenticating uploads
Interactive developers usually rely on vg login. Automated environments such as CI typically authenticate with a DSN token instead, which you generate with vg dsn create and pass with --dsn. See Create a Data Source with vg dsn create and Push from CI Pipelines.
What you get
Once results land in Vibgrate Cloud, the dashboard shows your current DriftScore, the findings behind it, and a history you can use to track drift trends. Multiple repositories roll up into a portfolio view.
Troubleshooting
If an upload is rejected, confirm you are logged in (vg login) or that your DSN is valid. See Troubleshooting Push and Authentication.
Related
Connect a Repository to Vibgrate Cloud and Map Repositories to Applications.