Set Up a Portfolio View Across Repositories

Leadership rarely cares about one repository — they care about the portfolio. When every repo pushes its scans to the same Vibgrate Cloud workspace, the dashboard becomes an organization-wide view of where drift risk lives. This tutorial wires up that cross-repository view.

Prerequisites

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

Steps

1. Create a DSN per workspace

vg dsn create

Generate a DSN token for the shared workspace and store it as a CI secret in each repository so every pipeline can push non-interactively.

2. Add a push step to each repo

In each repository's pipeline, scan and push using the DSN.

vg scan --push --dsn "$VIBGRATE_DSN"

3. Label each repository

So repos are distinguishable in the dashboard, set the repository name on the push.

vg scan --push --dsn "$VIBGRATE_DSN" --repository-name my-service

4. Open the portfolio view

Go to dash.vibgrate.com and open the workspace. Each repository appears with its own DriftScore, side by side.

5. Compare repositories

Sort and compare DriftScores across the portfolio to find the repos with the most upgrade drift, and prioritize work accordingly.

Verification

Every repository that ran a push shows up in the workspace with a current DriftScore. If one is missing, confirm its CI step exited 0 and used the correct DSN and repository name.

Next Steps

• Roll the portfolio into a leadership update: "Generate an Executive Drift Summary".
• Keep every repo current: "Schedule Recurring Drift Reporting".