Your AI writes code against deprecated APIs. Stop babysitting its guesses.
Vibgrate AI Context serves your assistant version-correct library docs, a map of your own code, and where your stack has drifted — local, offline, nothing uploaded. So the code it writes matches the libraries you actually run, and the DriftScore shows you the picture before you open the PR.
Free Vibgrate CLI · results in about 60 seconds · offline · no sign-up · nothing uploads unless you push it
# Run without installing anything
npx @vibgrate/cli scan
# Pin a version or see every command
npx @vibgrate/cli@latest --helpno install·Nothing is installed globally — ideal for CI or a one-off scan.
Your first 10 minutes
Free CLI, no sign-up. Nothing uploads unless you push it.
One command, no install. A 0–100 DriftScore for the repo, with findings ranked by severity — in about 60 seconds.
What depends on the thing you're about to change, and which tests to run — before you open the PR.
Vibgrate AI Context serves version-correct library docs, your code map, and drift to your AI assistant — local, offline, nothing uploaded.
Stop Guessing. Start Knowing.
Every developer has been there: you update a dependency expecting a version bump, then spend the afternoon chasing breaking changes through the codebase. Hours of debugging. Missed deadlines.
Vibgrate shows you the picture before you touch a manifest: which packages are outdated, how far behind they are, and which upgrades carry breaking-change signals in their release notes.
- DriftScore 0–100 per project: runtime lag, framework majors behind, dependency age, EOL proximity
- Breaking-change signals read from release notes between your version and the latest
- vg impact <name> — what depends on it and which tests to run
- vg why <package> — who introduced it, every version change, open vulnerabilities
Why Developers Love Vibgrate
An AI Assistant That Reads the Right Docs
Vibgrate AI Context (vg serve) serves version-correct library docs, your code map, and drift to your AI assistant — local, offline, nothing uploaded. It writes against the versions you actually run, not the ones it half-remembers.
A Map Your AI Can Trust
Vibgrate Graph builds a code map across 19 languages, and vg impact <name> shows what depends on the thing you're about to change — and which tests to run before you push.
Know Where a Dependency Came From
vg why <package> shows who introduced a dependency, every version change since, and its open vulnerabilities.
DriftScore as Proof
A bare vg scans the current directory and returns a DriftScore from 0 to 100 — runtime lag, framework majors behind, dependency age, EOL proximity — with findings ranked by severity, in about 60 seconds.
Breaking Change Detection
Not every outdated package costs the same. Vibgrate reads the release notes between your version and the latest and flags breaking-change signals — BREAKING markers, removals, migrations, dropped runtimes — so you know which upgrades are version bumps and which are projects.
Then vg impact shows what depends on the thing you're changing and which tests to run. Your estimate comes from evidence, not optimism.
Scan Your Project Now
Run npx @vibgrate/cli scan in any repo — results in about 60 seconds, offline capable, no sign-up. Nothing uploads unless you push it.
Prefer to install? Every install method is on the CLI page →