What it does
Paste code, for example an answer from an AI assistant, and the tool lists lines that match well-known insecure patterns. Each finding shows the line, why the pattern matters, a safer alternative and, where the mapping is certain, a CWE number. You can switch single rules off, filter by severity, copy a Markdown report, or export the findings as SARIF 2.1.0 text.
What it checks
- JavaScript and TypeScript:
evalandnew Function;innerHTML,outerHTML,insertAdjacentHTMLanddocument.writewith a non-constant value;dangerouslySetInnerHTML;execorexecSyncbuilt from a template string or concatenation;Math.randomnear words such as token, secret, password, session or id; MD5 or SHA-1 near a password;rejectUnauthorized: falseandNODE_TLS_REJECT_UNAUTHORIZED=0; CORS origin*together with credentials; JWTignoreExpirationand thenonealgorithm; SQL built with template strings or concatenation;res.redirectwith request values;target="_blank"withoutrel; tokens stored inlocalStorage. - Python:
evalandexec;pickleandmarshalloading;yaml.loadwithout a safe loader;subprocesswithshell=Trueandos.systemwith built strings;verify=Falseand unverified SSL contexts; MD5 or SHA-1 near a password; therandommodule near secrets;assertused for security checks;DEBUG = Trueand Flaskdebug=True; SQL built with f-strings,%,.format()or+;tempfile.mktemp. - SQL:
UPDATEorDELETEwithoutWHERE,DROP,TRUNCATEandGRANT ALL. - Shell: a download piped into a shell,
chmod 777, andcurl -kor--no-check-certificate. - Several languages: passwords, secrets, tokens and API keys written into the code as string values. Obvious placeholders such as
changemeare ignored.
How comments and strings are handled
Text inside comments and inside string literals is not treated as code, so // eval(x) or 'eval(x)' is not flagged. JavaScript is read with the site's JavaScript lexer. If the lexer cannot read the text (TypeScript types, JSX or unusual syntax can cause this), a simpler scanner is used and a note says so. Python, SQL and shell use a small comment and string scanner. Some rules look inside strings on purpose, for example for SQL text, HTML links or the name of an environment variable. A value counts as constant when it is only string literals; el.innerHTML = '<b>ok</b>' is not flagged.
What it cannot catch
- Data flow. The tool does not know where a variable came from.
exec(cmd)is not flagged even whencmdholds user input, and a flagged line may in fact use a trusted value. - Missing protection. It does not find missing authentication, missing authorization, weak access rules, race conditions, business-logic flaws or vulnerable dependencies.
- Other languages and frameworks. Only the four languages above are covered, and only the listed patterns. Other APIs that do the same thing are not recognised.
- Unusual formatting. Code built across files, aliased imports, code generated at run time and heavily minified code can hide a pattern or cause a false alarm.
- A clean result is not proof that the code is safe. Use a real SAST tool such as Semgrep or CodeQL, code review and tests for anything that matters.
Limits
Code up to 1,000,000 characters is checked, in a background Web Worker so the page stays responsive; 200 KB is usually done well under a second. Each rule reports at most 200 matches, at most 2,000 findings are kept in total, and the list shows the first 300 (the reports include all findings that match the filter).
SARIF and Markdown
SARIF 2.1.0 is the common format for static-analysis results. The export contains the rules that fired and one result per finding with its line and column, so it can be saved as a .sarif file and loaded into tools that read SARIF. Nothing is uploaded: the JSON is only text in the box.
Example: six findings in eleven lines
The built-in example is a small JavaScript login handler. The linter finds 3 high-severity and 3 medium-severity issues, each with a CWE reference, an explanation and a safer alternative:
- High, CWE-79:
innerHTMLset from a non-constant value built fromreq.query.name. - High, CWE-89: a SQL query built by concatenating
req.query.id. - High, CWE-798: an API key written into the code.
- Medium, CWE-338:
Math.random()used to create a token. - Medium, CWE-601:
res.redirect()with a value from the request. - Medium: a token stored in
localStorage.
The same example also contains code that is not reported: eval(userInput) inside a comment, eval(x) inside a string and an innerHTML assignment of a constant string. They are ignored on purpose, which keeps the noise down. 42 rules are available and you can turn rules on or off. Reports can be copied as Markdown or exported as SARIF 2.1.0 for other tools.
Frequently asked questions
Does this replace Semgrep, CodeQL or a security review?
No. The result is a set of pattern matches, not proof of a vulnerability, and there is no data-flow analysis. Use it as a quick first pass on code you pasted from an assistant or a forum.
Which languages does it check?
JavaScript, TypeScript and Python. The language is detected automatically, and you can also choose it yourself.
Can it miss problems?
Yes. A clean result only means that none of the patterns matched.
Is my code uploaded?
No. The code is checked on your device.
Privacy
This tool runs entirely in your browser. What you enter is processed on your device and is not sent to a server. The page does not write your input to local storage, cookies or the URL, and the code is never run.