All demosSemantic Linter
Semantic Linter
Find potential injections and hardcoded secrets in sample code, with findings linked to the affected lines.
Powered by/yes-no/classify
Performance & cost
This page session · since page load
- Typical request time
- —
- Input tokens
- 0
- Estimated cost · USD
- $0.00
How these numbers work · 0 successful requests
- Model compute
- —
- Successful requests
- 0
Average per measured successful request.
Run the demo to measure live requests.
Request time is the median time for a successful request, including queue, network, and retries. One request can judge many inputs: model compute adds their processing time and can exceed browser time.
Input tokens come from API response headers. Cost is estimated at $0.04 per million input tokens, before plan credits. Missing usage is marked unavailable or as a partial total (≥). Demo resets keep these totals; reload the page to start a new session.
Choose a sample file and select Scan file, then open a finding to inspect it.
How it works
The model judges code lines in batches. Local syntax checks narrow the findings to supported patterns, and the editor marks lines that clear the reporting threshold. Auto-lint can check edits as you type.
Demo scope
This demo has a narrow scope: injections and hardcoded secrets. It does not detect logic, null-handling, error-handling or performance defects. Scores can vary with batch contents; review each finding.
Inspired by the work of dabit3.