Vibgrate for VS Code

Your codebase has a number. Now it's in your editor.

Every stack drifts: runtimes reach end of life, frameworks fall majors behind, dependencies go quiet. Most teams find out during the upgrade that hurts. Vibgrate for VS Code shows you the drift as you work — a DriftScore in the status bar, computed on your machine, with per-dependency detail in your manifests.

Install the extension, open a workspace, and the score appears. No account. No token. Nothing to configure.

One build works in VS Code, Cursor, Windsurf, and Eclipse Theia (published to both the VS Code Marketplace and Open VSX).

What is a DriftScore?

The DriftScore is a 0–100 measure of how far your stack has drifted from current, supported versions — runtimes, frameworks, and dependencies. 0 means no drift; 100 means maximum drift. Scores fall into three bands: low (0–30), moderate (31–60), and high (61–100). The methodology is published and versioned.

What you see

Status bar — your workspace DriftScore, colored by band, always current.
Inline detail — each dependency line in package.json shows how far behind it is, the latest version, and how stale it has gone. Configurable: full, compact, or off.
Overview ruler — colored marks in the scrollbar show the whole file's drift at a glance.
Explorer badges — a score badge on manifest files in the file tree.
DriftScore panel — the full breakdown, one click away in the activity bar.
Hovers — version currency, majors behind, package age, and license for any dependency.
Route This Fix… — when you decide to act, a ranked list of remediation routes (Renovate, OpenRewrite, and others) ordered by technical fit for your case.

All colors adapt to your theme, including light and high-contrast themes.

Local by design

Your code stays on your machine. Drift scanning reads manifests and lockfiles only — it does not read or upload your source code.
No account, no token. The full local DriftScore works without signing in to anything.
The engine is bundled. The first scan works offline, with nothing to download — including on Remote-SSH, in devcontainers, and behind a corporate proxy.

Quiet by design

Drift is not urgent the way a security alert is, and a tool that nags gets uninstalled. So this extension shows no toasts, no modals, and no notifications. Problems-panel diagnostics are off by default; when you turn them on, they report three hard facts only — end-of-life runtimes, unmaintained packages, and license changes — and never at Error severity. Vibgrate measures; it does not gate your work.

Works with your AI assistant

If you use an AI coding assistant — Claude Code, Cursor, Codex, Gemini CLI, Windsurf, Copilot, Aider, Grok CLI, and others — the extension notices and wires Vibgrate AI Context into it in the background (the same setup as running vg install --all yourself): a skill, an MCP registration where the assistant supports one, and a short advisory note, so your assistant answers from your code map and real dependency versions instead of guessing. It runs once per workspace, silently, and only when an assistant is actually in use. Two settings control it: turn off vibgrate.aiContext.autoInstall to stop the automatic setup, or turn off vibgrate.aiContext.enabled to remove the wiring again (the same as running vg uninstall).

The extension also builds the local Vibgrate Graph — the code map behind the panel's Graph section — in the background. Turn it off with vibgrate.graph.enabled. Semantic search over the graph uses a small local search backend and embedding model, downloaded only after you confirm; turning off vibgrate.graph.semanticSearch keeps queries lexical and removes both downloads.

The same number everywhere

The extension renders scores computed by the Vibgrate CLI — the same engine that powers vg in your terminal. The score in your editor matches the score in your CI output and on your dashboard, because it comes from the same place. To try the engine directly, run npx @vibgrate/cli scan in any repository, or point the vibgrate.cliPath setting at your own vg install.

Settings

Setting	Default	What it does
`vibgrate.statusBar`	`true`	Show the DriftScore in the status bar.
`vibgrate.inlineDetail`	`full`	Per-dependency end-of-line detail: `full`, `compact`, or `off`.
`vibgrate.explorerBadges`	`true`	Score badge on manifests in the Explorer.
`vibgrate.diagnostics`	`false`	Problems-panel entries for EOL runtimes, unmaintained packages, and license changes.
`vibgrate.cliPath`	`""`	Path to your own Vibgrate CLI (`vg`). Empty uses the bundled engine, then `vg` on PATH.
`vibgrate.graph.enabled`	`true`	Build and serve the local Vibgrate Graph (the panel's Graph section). Off skips the background build.
`vibgrate.graph.semanticSearch`	`true`	Semantic search over the graph. Off keeps queries lexical and removes the downloaded local embedding model and backend.
`vibgrate.aiContext.enabled`	`true`	Keep Vibgrate AI Context wired into your AI assistants. Off removes the wiring (`vg uninstall`).
`vibgrate.aiContext.autoInstall`	`true`	When an AI assistant is detected, wire Vibgrate AI Context automatically (`vg install --all`), once per workspace.

Commands

Vibgrate: Rescan Workspace
Vibgrate: Open DriftScore Panel
Vibgrate: Route This Fix…
Vibgrate: Show Language Server Log

Free and paid, plainly

Everything this extension shows — the DriftScore, inline detail, the panel, hovers — is free, with no account. A Vibgrate Cloud account adds score history, trends, and team rollups. Automated remediation (vg fix) is a separate paid capability; it appears in Route This Fix… ranked on technical fit like every other route, labeled as paid, with no special placement. The score never advertises the fix.

Learn more

vibgrate.com — the Vibgrate platform
Vibgrate Cloud — history, trends, and team rollups
Report an issue