Vibgrate scans your repositories for drift — how far your code, dependencies, and frameworks have fallen behind current versions — and turns that into scores, risks, and fixes you can act on. This guide gets you from an empty dashboard to your first results.
Connect a repository
Vibgrate needs access to your code before it can scan it.
- Open Settings, then Source control.
- Connect GitHub, GitLab, or Bitbucket.
- Select the repositories you want Vibgrate to track.
You can also scan locally with the Vibgrate CLI and ingest the result — useful for private or air-gapped code.
Run your first scan
Once a repository is connected, open the Scans tab and start a scan. Vibgrate analyzes the repository and produces a drift score, a list of findings, and upgrade opportunities. The first scan usually takes a minute or two.
Read your results
- Executive Overview gives you the headline — estate drift, high-risk repositories, and open vulnerabilities.
- Repositories and Applications show the detail behind those numbers.
- Risk & Compliance is where you triage what matters most.
A drift score runs from 0 to 100. Lower is better: 🟢 low (0–39), 🟡 moderate (40–69), 🔴 high (70–100). Drift is normal — every codebase has some. The dashboard is here to help you manage it, not to grade you.
Where to go next
- Set a drift budget to get warned when an application drifts too far.
- Turn findings into fixes under Remediation.
- Ask the Pulse chatbot anything — it can read your live data and point you to the right tab.