How much upgrade risk is hiding across your repos?
Vibgrate gives every repo one 0–100 DriftScore — trended over time and rolled up across the portfolio — so you can see where risk is building and govern it. It reads your manifests and lockfiles, never your source.
Free CLI · runs locally · reads manifests, never your source
Your first 10 minutes
Free CLI, runs locally. It reads your manifests and lockfiles — never your source. Nothing uploads unless you push it.
A bare vg scans the current directory and returns one 0–100 DriftScore, plus the shared code map — locally, reading your manifests and lockfiles, never your source.
The repo becomes a tile in the portfolio view in Vibgrate Cloud, with its DriftScore trended over time so you can watch risk build or fall.
Portfolio DriftScore, risk distribution, and tech-stack governance across every repo — the demo opens with example data, no sign-in, no card.
Portfolio Risk You Can Actually See
As a tech lead or architect, you carry the question no dashboard answers today: how much upgrade risk is hiding across our repos? Dependencies fall behind, runtimes reach end of life, and complexity creeps in — quietly, across dozens of projects that each report differently.
Vibgrate gives every repo one 0–100 DriftScore on the same scale, trended over time and rolled up into a portfolio view in Vibgrate Cloud. And you never have to trust a black box with your code — the scanner reads your manifests and lockfiles, never your source, and runs locally until you choose to push a result.
- One 0–100 DriftScore per repo, on the same scale everywhere
- DriftScore trended over time — see risk build or fall
- Portfolio roll-up across every team and repo in Vibgrate Cloud
- Reads your manifests and lockfiles — never your source
Why Tech Leads & Architects Choose Vibgrate
Portfolio DriftScore, Trended
One 0–100 DriftScore per repo on the same scale everywhere, tracked over time and rolled up across teams — so you can see where risk is building and where it is falling.
Tech-Stack Governance
Every scan records the frameworks, runtimes, and tools each repo uses. The technology radar in Vibgrate Cloud shows how they spread across the estate, so you can keep new projects on approved foundations.
Never Reads Your Source
Vibgrate reads manifests and lockfiles only — never your source. The CLI runs locally, nothing uploads unless you push it, and releases are signed across ~19 ecosystems.
A Shared Code Map
vg hubs shows the files everything depends on, vg areas groups the codebase into functional areas, and vg oddities flags files that do not fit the pattern. vg share commits a code map the whole team — and any AI — can read.
Tech-Stack Governance at Scale
Every scan records the frameworks, runtimes, bundlers, and tools each repo uses, and the technology radar in Vibgrate Cloud shows how they spread across the estate. Spot proliferation before it becomes unmanageable.
Compare tech stacks across projects to plan migrations and keep new projects on approved foundations — governed by portfolio-wide DriftScore, not gut feeling.
A Shared Map of the Codebase
Beyond the score, every scan builds a code map: layer classification for each source file, the hubs everything depends on, functional areas, and the oddities that do not fit the pattern around them.
Run vg share to commit that map — the same picture of the codebase in every teammate's hands, and readable by any AI assistant working in the repo. That map is Vibgrate Graph — free for every developer.
The map and the DriftScore are derived from your manifests, lockfiles, and file structure — Vibgrate never reads your source code.
See the Risk Across Your Portfolio
Tour Vibgrate Cloud with example data — no sign-in, no card. Or run vg in any repo to get your first DriftScore locally, in about 60 seconds.