01 /
Follow input to its destination
Review the input source, assignments, and path to a risky operation in diagnostic related information.
LLMSCAN / VS CODE / LOCAL STATIC ANALYSIS
Check whether LLM responses or external input reach SQL, shell commands, or HTML output. Analyze Python, TypeScript, JavaScript, and PHP locally, and review input-to-operation paths in VS Code.
LLM output / User input
↓
Variables & assignments
↓
SQL / Shell / HTML 01 /
Review the input source, assignments, and path to a risky operation in diagnostic related information.
02 /
Include LLM responses, agent tool-call arguments, and MCP tool arguments. Review places where model output is executed or rendered directly.
03 /
Use inline diagnostics, hover explanations, and Quick Fix while editing, then changed-file scanning and SARIF output in CI.
01 / FEATURE TOUR
LLM SECURITY SCANNER / 01
Analyze recognized response patterns from OpenAI, Anthropic, Gemini, Ollama, LangChain, LlamaIndex, and the Vercel AI SDK. Review how values are handled before they reach SQL, eval, shell execution, or innerHTML.
Read the guide on this page ↓// Illustrative input-to-sink path
const output = response.choices[0].message.content;
const query = output;
db.execute(query); LLM SECURITY SCANNER / 02
Opening a supported file triggers analysis, with inline diagnostics and Problems entries. Hover for explanations, safer patterns, and CWE references. Supported findings offer Quick Fix suggestions such as textContent or yaml.safe_load.
Read the guide on this page ↓// Avoid interpreting untrusted text as HTML
element.textContent = modelOutput; LLM SECURITY SCANNER / 03
Configure custom sources, sinks, sanitizers, exclusions, and confidence in .llmscan.yml. Record existing findings in a baseline, and use the CLI for changed-file scans and JSON or SARIF export.
Read the guide on this page ↓minConfidence: medium
failOn: high
baseline: .llmscan-baseline.json
exclude:
- "**/generated/**" 02 / FROM INPUT TO ACTION
Open a supported file to run local syntax analysis and input tracing within functions.
Jump to the affected line from the sidebar or Problems panel, and inspect the path to the risky operation.
Apply a Quick Fix or edit manually. Optionally copy the AI-ready Markdown instructions, review the changes, and rescan.
03 / COVERAGE
Python, TypeScript, JavaScript, and PHP. Review SQL, command and code execution, XSS, unsafe deserialization, and LLM05-related output handling.
Analysis centers on intraprocedural tracing with Tree-sitter WASM. Review findings from supported patterns and custom rules against the actual code and runtime context.
04 / GET STARTED
Install “LLMScan - AI Security Scanner” in VS Code 1.85 or later. Analysis requires no API key or external server.
Open a Python, TypeScript, JavaScript, or PHP file. Hover over diagnostics and review paths in Problems or the LLMScan sidebar.
Scan the workspace from the sidebar. Configure .llmscan.yml and baselines for your team, then recheck after remediation.
START WITH YOUR PROJECT
LLM Security Scanner
Tree-sitter WASM runs locally without automatically sending source code or filenames externally. Copying AI-ready Markdown writes to the clipboard. Review included code and paths before sharing it with an external AI service.
EXPLORE THE APPS / TIP
Choose an app to explore its features and how to use it.
Review code structure, technical debt, and security.
Explore the app
Generate dependency inventories and check known vulnerabilities.
Explore the app
Trace LLM output and external input to risky operations.
Explore the app