In your editor

Catch the vulnerabilities your AI assistant just wrote.

The BreachLens extension surfaces findings and fixes right in VS Code — including code that isn't in a repository yet. Review what your copilot just generated before it ever reaches a pull request.

Book a technical demo Read the docs

Works in VS CodeScans code before it's committedPoints at your BreachLens, not ours

The BreachLens extension in VS Code — a Findings tree in the sidebar, and a HIGH SAST SSRF-injection finding surfaced inline on the code with a one-key Fix action.

Shift left of the commit

AI writes code faster than you can review it.

Copilots generate insecure patterns at the speed of autocomplete, and the usual security tools only look after it's committed. BreachLens looks in the editor — even at code that isn't in a repo yet — so the bug never becomes a PR.

Install

One lightweight extension

Add the BreachLens extension to VS Code and point it at your own BreachLens deployment. The heavy scanning stays on the server.

Scan

As you write

Check the file you're editing — or a snippet that isn't saved anywhere yet — without pushing to a repo first.

Fix

Findings and fixes inline

See the issue and the proposed remediation in the editor, and act on it before you commit.

What you get

Security where the code is actually written.

Findings in the editor

No context-switch.

· Issues surface inline in VS Code, where you're already working.
· With the proposed fix, not just a red squiggle.
· Reviewed before the code leaves your machine.

Scan code without a repo

Even code that isn't saved.

· Check unsaved files or a pasted snippet.
· No need to push to a branch to get an answer.
· The right place to vet AI-generated code.

Catch AI-generated risk

Review the copilot.

· Vet what your AI assistant just wrote before it lands.
· The insecure pattern is caught in the editor, not in production.
· A guardrail for the way teams actually code now.

Lightweight by design

The heavy lifting stays server-side.

· A small extension — the scanners live on your BreachLens.
· Your code goes to your own deployment, never our cloud.
· Nothing bundled locally that you have to keep updated.

Straight answers

What a developer asks about the extension.

Which editors are supported?

VS Code today. JetBrains support is on the roadmap — we'll tell you where it stands rather than imply it ships now.

Does my code leave my machine?

It goes to your own self-hosted BreachLens for analysis — never our cloud. In an air-gapped setup, it never leaves your network at all.

Do I need the code in a repository first?

No. You can scan an unsaved file or a pasted snippet — which is exactly what you want when you're vetting code an AI assistant just generated, before it becomes a commit.

Why is the extension so small?

The scanners run on your BreachLens server, not in your editor. The extension is a thin client — nothing heavy to install locally, nothing to keep patched on every developer's laptop.