Docs

Quick start

Vise runs in your IDE, a Desktop app, and the CLI — same engine, same results, on Windows, macOS and Linux. Pick your surface. For the complete reference — every capability, option and example — read the full User Manual, or jump to the CI/CD integration guide.

The IDE extensions are self-contained. They run the vise-scan engine, and on your first scan the extension offers a one-click engine download (~50 MB, one-time, checksum-verified) — then everything runs fully offline. Already have the Desktop app or CLI? The extension reuses that engine automatically. Works on Windows, macOS and Linux (the Visual Studio extension is Windows-only, because Visual Studio is).

VS Code

  1. Install the Vise extension (or from the VS Code Marketplace).
  2. Where it is: a Vise icon appears in the Activity Bar (left edge) — click it to open the Findings panel.
  3. Scan: Command Palette (Ctrl/Cmd+Shift+P) → Vise: Scan Workspace — or the scan icon in the Findings panel, or right-click a folder → scan.
  4. Results: findings group by severity in the panel. Right-click one for Open · Explain · Fix with AI · Copy as AI prompt · Suppress.
  5. Settings: vise.cliPath, vise.edition, vise.licenseKey (table below).

JetBrains (Rider, IntelliJ, PyCharm, Android Studio…)

  1. Install the plugin (JetBrains Marketplace, or Settings → Plugins → install from disk).
  2. Where it is: a Tools → Vise menu, plus a Vise tool window docked at the bottom.
  3. Scan: Tools → Vise → Scan Project (Ctrl+Alt+Shift+S) — or right-click in the editor / project tree → Scan with Vise.
  4. Results: the bottom Vise tool window, grouped by severity, plus inline highlights. Right-click a finding for Explain / Fix with AI / Suppress.
  5. Settings: Settings → Tools → Vise (edition, license key, scan-on-save).

Visual Studio (2022 & 2026)

  1. Install the .vsix (double-click it, or from the VS Marketplace) and restart Visual Studio.
  2. Where it is: everything lives under the Tools → Vise menu.
  3. Open the panel: Tools → Vise → Vise Panel — the Vise tool window opens (dock it wherever you like).
  4. Scan: Tools → Vise → Scan Solution (Ctrl+Alt+Shift+S) or Scan Current File — or right-click a file in Solution Explorer → Scan File.
  5. Results & actions: findings show in the Vise panel; right-click in code for Vise: Explain finding · Copy AI fix prompt · Suppress this line.
  6. Settings: Tools → Options → Vise (license key, CLI path, edition).

Desktop app

  1. Open the Vise Desktop app.
  2. Scan: drop a project folder onto the window (or pick a recent one) → Scan.
  3. Results: a Dashboard (severity donut + OWASP-category split) and a Vulnerabilities list — each finding mapped to OWASP / CWE / CVSS with a recommended fix and Ask AI / Get Fix.
  4. Quick Wins & Export: the top buttons rank fixes by impact ÷ effort and export reports.
  5. Activate: Settings → License (see Activating Pro / Enterprise below).

CLI

vise-scan ./my-project --edition pro --format sarif --output report.sarif

Exit codes: 0 clean · 1 medium/low · 2 critical/high · 4 license · 5 scan error.

CI/CD

The vise-scan CLI is a single self-contained binary (Linux · macOS · Windows). One step in GitHub Actions — download, checksum, scan, gate and SARIF upload all handled:

- uses: visesec/vise-action@v1
  with:
    path: .
    ci-token: ${{ secrets.VISE_CI_TOKEN }}
    min-severity: medium
    upload-sarif: true

CI/CD runs require Enterprise and a machine-unbound VISE_CI_TOKEN (issued for your Enterprise account — reply to your license email or contact support) — not a seat key, which binds to a single machine. Gate on exit code ≥ 2 (Critical/High found).

Full cross-platform recipes — GitHub Actions, GitLab, Azure DevOps, Jenkins, Bitbucket, Docker, checksum-pinned, with SARIF integration and best practices — are in the CI/CD integration guide.

Settings (VS Code)

SettingDefaultDescription
vise.cliPath""Path to vise-scan (empty = auto-detect)
vise.editionbasicbasic · pro · ent
vise.licenseKey""Pro / Enterprise key
vise.scanOnSavefalseScan the current file on save
vise.showInProblemsfalseAlso show inline squiggles + Problems entries

Tiers

Free = regex + IDE/CLI · Pro = AST + Desktop + AI fix · Enterprise = taint + CI + SARIF/SBOM. See pricing.

Activating Pro / Enterprise

After you buy on the pricing page, your license key arrives by email — and the activation page gives you one-click buttons: Open in Vise Desktop and Open in VS Code activate for you, nothing to copy. Activation is a one-time online step that binds the key to your machine; after that, every scan runs fully offline. One activation per machine covers all surfaces — Desktop, IDE and CLI share it.

Or sign in with your email instead of a key: Desktop and the IDE extensions have a Sign in with email action (CLI: vise-scan --login <you@email>) that emails you a one-click link — open it and Vise activates without a key to copy.

Prefer to paste it yourself?

  1. Desktop appSettings → License, paste the key — it activates the moment you paste.
  2. VS Code — the Open in VS Code button, or Settings → vise.licenseKey = your key.
  3. JetBrains / Visual StudioSettings/Options → Vise → License key.
  4. CLI — run vise-scan --license-key <KEY> once (or set VISE_LICENSE_KEY); it persists for later runs.

Enterprise — seats & CI: seats are claimed per developer by email; each developer activates on their own machine. The license owner manages seats and allowed members at visesec.com/team. Pipelines use the separate machine-unbound VISE_CI_TOKEN (see CI/CD above) — never a seat key.

Activation is automatic and per-machine — nothing to configure. Changing machines or need a hand? Support can move your license. Full step-by-step: the activation page and the User Manual.