Audit every editor on your machine.
Find extensions across VS Code, Cursor, Windsurf, and VSCodium. Inspect an integrity-checked local snapshot without executing the extension or sending its source to GuardRails.
$ pipx install guardlensguardlens Command: guardrails Python 3.11+ One self-contained, integrity-checked packagelocal extension auditprivate$ guardrails
Installed extensions 143 detected› Select an extension to inspect
Two ways to inspect an extension. One evidence standard.
Choose the product based on where the extension is. The analysis boundary stays clear.
Check a package before it reaches an editor.
Search the Marketplace or submit a package for a managed Deep Scan with a shareable report.
Best for evaluating an extension before installation.Open website Deep ScanCheck what is already installed.
Find extensions in VS Code, Cursor, Windsurf, VSCodium, and Insiders, then inspect local snapshots on your machine.
Best for auditing the editor you use today.Install Guardrails CLIFor the same artifact, a properly configured CLI Deep Scan uses the same analysis boundary as website Deep Scan.
Your extension code stays on your machine.
Guardrails copies selected extensions into a temporary private snapshot, scans it locally, then removes the snapshot. It never launches extension code.
Source files and package contents are not sent to Guardrails.
The scanner is bundled with Guardrails and checked for unexpected changes before it runs.
Deep mode can query Marketplace, dependency, and repository metadata using IDs, versions, dependencies, and URLs.
Install once. Start with the extensions you already trust.
The interactive command groups installed extensions by IDE, lets you search before scanning, and produces findings, risk scoring, coverage, and exportable reports.
- 01Install the CLI
pipx install guardlens - 02Open the local scanner
guardrails - 03Use Deep Scan when needed
pipx install "guardlens[analysis]"
$ pipx install guardlens