Scans is where you run analyses and watch them complete. Each scan reads a repository, calculates its drift score, and records findings, vulnerabilities, and SBOM coverage. This tab is the operational heartbeat — what ran, whether it succeeded, and how drift is trending.
Run a scan
- Open the Scans tab.
- Select New scan and choose a connected repository.
- Start the scan.
Vibgrate runs the analysis and updates the dashboard when it finishes. The first scan of a repository usually takes a minute or two; later scans are faster.
Read a scan
Each scan shows its drift score, risk level, ingest status (pending, completed, or enriched), and the findings it produced. Open a scan to see the full breakdown — projects, score components, vulnerabilities, and VCS metadata.
When a scan fails
If a scan doesn't finish, the most common cause is an expired or revoked repository connection. Reconnect the repository under Settings → Source control, then run the scan again. The error detail on the scan record names the specific cause.
Scheduling
You don't have to run every scan by hand. Scheduled scans keep connected repositories up to date on a cadence you choose, so your drift scores never go stale.