Vibgrate Cloud Upload and Trend Tracking: From One-Off Scans to Portfolio-Wide Drift Intelligence

The Limits of One-Off Scans

Running vibgrate scan gives you a precise, actionable picture of your drift posture right now. For a single project that you check occasionally, that might be enough.

But for organizations managing dozens or hundreds of repositories, one-off scans create a fragmented picture. You need:

• Trends: Is drift improving or worsening month over month?
• Portfolio comparison: Which of our 50 repositories has the worst drift? Where should we invest upgrade effort?
• Historical context: When did drift start worsening? Does it correlate with team changes, roadmap shifts, or specific PRs?

Vibgrate Cloud provides all of this — and it starts with a single flag: --push.

Pushing Scan Results

To upload a scan result to the dashboard, add --push to your scan command:

VIBGRATE_DSN="vibgrate+https://<key_id>:<secret>@us.ingest.vibgrate.com/<workspace_id>" \
  npx @vibgrate/cli scan --push

Or upload an existing artifact:

VIBGRATE_DSN="..." npx @vibgrate/cli@latest push --file .vibgrate/scan_result.json

The DSN (Data Source Name) is your authentication token. It tells the CLI which workspace to upload to and authenticates the request with HMAC signing.

Setting Up a DSN

Get your DSN from dash.vibgrate.com, or generate one from the CLI:

vibgrate dsn create --workspace <your-workspace-id> --region us

Critical: Never commit your DSN to version control. In CI, store it as a secret:

# GitHub Actions
env:
  VIBGRATE_DSN: ${{ secrets.VIBGRATE_DSN }}

Data Residency

Vibgrate supports region-specific ingest endpoints:

Use --region eu if your data governance requires European data residency:

vibgrate push --file .vibgrate/scan_result.json --region eu

What Vibgrate Cloud Shows

Once scan results are flowing to the dashboard, you get:

• Score trends over time: A line chart showing your drift score across weeks and months.
• Portfolio comparison: All your repositories ranked by drift score, making it easy to identify the worst offenders.
• Component breakdown trends: See whether runtime, framework, dependency, or EOL risk is driving changes.
• Finding history: Track which findings appeared, persisted, or were resolved.

Upload Is Always Optional

This is important: the CLI provides full value locally without any server connection. Dashboard upload is opt-in. If you never run --push, no data ever leaves your machine.

The Vibgrate Code Intelligence Engine is designed privacy-first. Local analysis is the default. Dashboard upload is an optional enhancement for teams that want organizational visibility.

See the big picture. Sign up at dash.vibgrate.com to connect your repos, push scan results, and track drift trends across your entire engineering portfolio.