Vibgrate for VS Code — free, no account, no upload

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 — and most teams find out during the upgrade that hurts. Vibgrate for VS Code shows the drift as you work: a DriftScore in the status bar, computed on your machine, with per-dependency detail in your manifests.

Install Get the CLI

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

What you see

Install the extension, open a workspace, and the score appears. Nothing to configure. All colors adapt to your theme, including light and high-contrast themes.

Status bar score

Your workspace DriftScore, colored by band, always current — computed locally as you work.

Inline dependency detail

Each dependency line in your manifest shows how far behind it is, the latest version, and how stale it has gone. 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, so drift is visible before you open the file.

DriftScore panel

The full breakdown one click away in the activity bar — plus a Graph section for asking your code map questions.

Hovers

Version currency, majors behind, package age, and license for any dependency, on hover.

When you decide to act, Route This Fix… shows a ranked list of remediation routes (Renovate, OpenRewrite, and others) ordered by technical fit for your case.

Local by design

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.

First scan works offline

The engine is bundled with the extension, so the first scan works offline with nothing to download — including on Remote-SSH, in devcontainers, and behind a corporate proxy.

Quiet by design

No toasts, no modals, no notifications. Problems-panel diagnostics are off by default, 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, and others — the extension notices and wires Vibgrate AI Context into it in the background, the same setup as running vg install --all yourself. 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 — settings turn it off or remove the wiring again.

Your code map, in the panel

The extension also builds the local Vibgrate Graph in the background — the code map behind the panel’s Graph section. Ask it plain-English questions, trace the blast radius of a change, or find how two symbols connect. Semantic search over the graph is opt-in: a small local search backend and embedding model download once after you confirm, then work offline. Turning the setting off 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.

Try the engine directly

$ npx @vibgrate/cli scan

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.