VS Code extension
Vipe for VS Code
Vipe catches exposed secrets, SQL injection, missing auth checks and duplicate definitions as you write. In the files you have open that is free, unlimited, and entirely on your machine. Vipe Pro scans the whole project, which adds unprotected Supabase tables, broken imports and unused code, and fixes what it finds in one click, with your first 5 fixes free. For security findings, Vipe writes the fix and explains the risk.
The extension isn't published yet. This page links to the VS Code Marketplace and Open VSX on launch day.
Or try it without installing: scan a project online
How it works
Free in the files you open. Pro for the whole project and fixes.
- Free forever
Flags issues as you code
Vipe checks the files you have open, as you type: 22 of the 24 security checks (exposed secrets, SQL injection, missing auth checks, unverified Stripe webhooks and more) and duplicate definitions inside a file. Unlimited, offline, no account.
- 5 free fixes, then Pro
Scans the project and fixes it
Vipe Pro scans the whole project in the background, including files your AI tools write to disk, with all 24 security checks and 3 build checks (broken imports, duplicate definitions, unused code). A fix is one click: Vipe shows the diff, explains the risk in plain English, and checks the file again afterwards. Your first 5 fixes are free.
- Private
Your code stays yours
Detection and build fixes happen on your machine; for a build fix, Vipe is only told that one fix was used. An AI fix sends just the handful of lines around the finding, and nothing is stored.
Coverage
What Vipe checks (and what it doesn't)
Vipe checks JavaScript and TypeScript files, SQL files, and environment files (.env). A safety net for the mistakes AI coding tools make most often. Not a full security review, and not a guarantee: no findings does not mean the code is secure. Some checks are certain and shown as errors. Others are likely, because they depend on something one file does not show, and are shown as warnings.
Free checks the files you have open. The checks marked “Project scan · Pro” compare files or read the whole project, so they run with the project scan in Vipe Pro.
24 security checks
Hardcoded secret
A real key format anywhere in a string (Stripe, OpenAI, Anthropic, GitHub, AWS, a private key, a Supabase service-role key), a secret-named variable holding a random-looking value, or a secret read from the environment with a default written in the code.
Error or warningSecret exposed to the browser
A secret behind a prefix that ships it to every visitor (NEXT_PUBLIC_, VITE_, REACT_APP_, EXPO_PUBLIC_), in code or in a .env file.
Error or warningService role key in browser code
The Supabase service role key, or the admin API that needs it, used in code that runs in the browser.
ErrorSecret written to logs
A log statement that prints the whole environment or a secret environment variable as it is.
ErrorEnvironment file not git-ignored
A .env file with values in it that no .gitignore rule covers, so git would commit it.
Error or warningEditor onlyProject scan · ProTable without row level security
In SQL migrations: a public table that no migration enables row level security for, row level security switched off, or a policy that lets anyone write.
Error or warningProject scan · ProSQL injection
A value spliced into the text of a SQL query instead of being passed as a parameter.
ErrorUnverified Stripe webhook
A Stripe webhook handler that acts on an event without verifying its signature.
Error or warningServer action without an auth check
A Next.js server action that changes data without checking who is calling it.
WarningRoute handler without an auth check
A Next.js route handler under an admin path, one that changes a record named by the request, or one that hands out a whole table of users or payments, with no check of who is calling.
WarningExpress route without auth
An Express route on a sensitive path with no authentication middleware.
WarningToken decoded without verification
Server code that decodes a login token without verifying it, or accepts tokens nobody signed.
Error or warningInsecure session cookie
A session or auth cookie set without the httpOnly and secure flags.
Error or warningUnsanitized HTML
Content rendered as HTML (dangerouslySetInnerHTML, innerHTML) that is not a fixed string, sanitized or generated.
WarningCode execution from request input
eval() or new Function() called with something that comes from a request.
Error or warningInsecure CORS
Any website allowed to call the API together with cookies or credentials.
ErrorWeak password hashing
A password hashed with MD5 or SHA1, or with a fast hash such as SHA-256.
ErrorPassword compared as plain text
A stored password compared directly with the one that was typed, which means it is stored unhashed.
WarningGuessable token
A token, a code or a password made with Math.random(), which can be predicted.
WarningOpen redirect
A redirect to an address taken straight from the request, with nothing checking where it leads.
Error or warningServer-side request forgery
Server code that fetches an address taken straight from the request, so the caller decides which machine the server talks to.
Error or warningPath traversal
A file read, written or deleted at a path built from a value in the request, with nothing keeping it inside its folder.
Error or warningCommand injection
A shell command (exec, execSync) built from a value in the request.
Error or warningWhole request body stored
The whole request body written to the database as it came, so the caller chooses which columns are set.
Warning
3 build checks
Broken import
An import of a file or an export that does not exist in the project.
WarningProject scan · ProDuplicate definition
The same name declared twice in one file, or the same Express route registered twice.
WarningUnused code
An import that is never used, or a function that nothing in the project references.
WarningProject scan · Pro
What it does not check
- Whether a signed-in user may see or change a particular record (authorization logic).
- Authentication done in middleware or in another file: a route that is protected there can still be reported.
- Input validation and rate limiting.
- A value from the request that passes through a helper function or another file before it is used: redirects, server-side fetches, file paths, shell commands and database writes are only followed inside one function.
- Languages other than JavaScript, TypeScript and SQL.
- Anything that needs following a value through more than one step of the code.
Pricing
Free to catch. Pro to fix.
Live detection in the files you open is free, unlimited and offline. The scan of your whole project and fixes (security and buildability) are included in Vipe Pro, with your first 5 fixes free. Vipe Pro is $12 a month.
Free
Catch problems in the files you work on.
- Live detection in the files you open: 22 security checks and duplicate definitions. Unlimited, offline, no account needed
- A notification when a file written outside the editor has a certain security issue, with the issue count for the whole project
- 5 fixes to try, security or build issues, with a GitHub sign-in
Pro
The whole project scanned, and problems fixed for you.
- Everything in Free
- Whole-project scan in the background: all 27 editor checks, including the ones that compare files
- 300 AI fixes a month (security). Unlimited detection and build fixes
- Every fix is checked: Vipe scans the file again and tells you if the issue is not resolved
- A plain-English explanation with each AI fix
- Cancel anytime — Pro runs to the end of the paid month
Prices in USD · Secure checkout via Stripe · Manage or cancel anytime from your account
Questions
Good to know
What is free, and what is Pro?
Free: live detection in the files you have open, unlimited and offline, with no account. Pro: the scan of your whole project (files you have not opened, and the checks that compare files) and fixes: 300 AI fixes a month, and unlimited build fixes. Every account gets 5 fixes to try.
Does my code leave my machine?
Not for detection or build fixes — those run inside your editor. Applying a build fix only tells Vipe that one fix was used, so it can be counted: no code, no file names. When you ask for an AI fix to a security finding, the few lines around it are sent to Vipe and to our AI provider, Anthropic, to write the fix. They are not stored.
Are build-issue fixes free?
Duplicate definitions inside a file are flagged for free in the files you open. Broken imports and unused code need the whole project, so they are found by the project scan in Vipe Pro. Fixing a build issue works like fixing a security finding: your first 5 fixes — of either kind, counted together — are free, then fixes are included in Vipe Pro. You need to be signed in to apply a fix; you never need to sign in to see problems in the files you open.
Which build issues get a one-click fix?
The ones with a safe, mechanical fix: an import that is never used, an import path that is one typo away from a single real file, a name that is one typo away from a single real export, and a name or route declared twice in the same file. Anything that needs a judgement call — code that only looks unused, or a duplicate across files — is flagged but left for you to decide. Every fix is a normal edit you can undo with Ctrl+Z.
What counts as one of my 5 free fixes?
A fix that is actually delivered: an AI fix for a security finding that comes back with a change you can apply, or a build-issue fix that is applied to your file. If Vipe can't produce a fix, or the edit can't be applied, it isn't counted. After a fix is applied Vipe checks the file again: if the issue is still reported, or the fix brought a new one, you are told and can undo it, and a free fix is given back (up to 3 times per account).
How do I cancel Pro?
From your account→ Manage subscription. You keep Pro until the end of the month you've paid for, and you won't be charged again.
Does it work in Cursor, Windsurf or VSCodium?
Yes. Install it from Open VSX; signing in works the same way in every editor.
Support
Questions or bugs? See Support or email support@usevipe.com.