Vipr Code Analyzer for VSCode

Vipr analyzes JavaScript, TypeScript, React, and Next.js projects locally inside VSCode-compatible editors. It adds inline diagnostics, a sidebar dashboard, a file navigator, optional AI-assisted workflows, and paid report surfaces for deeper historical and framework-specific analysis.

Free vs Pro

Vipr for VSCode has two public plans.

Plan	Included
Free	Core overview and dead-code reports, TypeScript reports, React overview, Next.js config checks, file navigator, dashboard, inline diagnostics, and incorrect-analysis reporting
Pro	React accessibility, anti-pattern, performance, reliability, and security reports; Next.js data-fetching, rendering, route-structure, security, and server/client reports; linting reports; history, regression, and trend surfaces; budget alerts

Notes:

AI availability depends on the editor and the installed chat provider. AI is not the same as Pro.
Some internal or custom licenses may unlock additional Enterprise-only reports. Those are not part of the public VSCode plan.

Licensing

Paid access is activated from the Command Palette, not from a raw settings field.

Run Vipr: Activate License.
Paste the purchase key you received from Vipr checkout.
Vipr exchanges that key for a signed, machine-bound claim and stores it in VSCode SecretStorage.
Run Vipr: Deactivate License before moving the license to another machine so the activation slot is freed server-side.

Important details:

Purchase keys are entered only through the masked activation prompt and are never stored in VS Code settings.
The signed machine claim is stored in VS Code SecretStorage. Vipr: Show License Status exposes a masked support reference with an explicit copy action, not the purchase key.
Pro access is validated against Supabase and refreshed periodically. A cached signed claim allows short offline use between refreshes.
VSCode licenses are version-scoped. A paid license covers the major version encoded in the claim returned by activation.

Issue Reporting

Users can report incorrect analysis directly from the extension:

Run Vipr: Report Incorrect Analysis
Or open an issue row in the dashboard and click Report issue

Reports go to the existing Supabase metric-feedback queue with editor/runtime metadata and the visible analysis context. Free users can add an optional contact email. No general support mailbox is required for this flow.

Editor Compatibility

Editor	Status
Visual Studio Code	Full extension surface. GitHub Copilot chat and language-model features work when the editor exposes the required APIs.
Cursor	Core analysis, dashboard, licensing, and issue reporting work. AI-specific behavior depends on Cursor's API compatibility.
Windsurf / VSCodium / other forks	Core local analysis should work, but Copilot-specific chat and language-model features may be unavailable or degraded.

Key Commands

Vipr: Analyze File
Vipr: Analyze Workspace
Vipr: Show Dashboard
Vipr: Show License Status
Vipr: Activate License
Vipr: Deactivate License
Vipr: View Pro Plans
Vipr: Show File History
Vipr: Find Regression
Vipr: Report Incorrect Analysis

Settings

Only the currently supported settings are documented here:

{
  "vipr.analyzeOnSave": true,
  "vipr.analyzeOnOpen": false,
  "vipr.showInlineHints": true,
  "vipr.showDecorations": true,
  "vipr.diagnosticSeverity": "all",
  "vipr.enableAiFixing": true,
  "vipr.aiProvider": "auto",
  "vipr.history.enabled": true,
  "vipr.debug": false
}

Privacy

Static analysis runs locally in the extension.
License activation, license refresh, and explicit feedback submission call Supabase edge functions.
AI requests are handled by the active editor/provider integration, for example GitHub Copilot in VSCode.

Vipr Frontend Analyzer

Vipr Development LLC