LLM API called directly from browser code
An OpenAI/Anthropic API call (or 'dangerouslyAllowBrowser: true') appears in client-side code. The API key ships in the bundle where anyone can extract it and run up your bill.
What the check contributes
Rule LLM001runs as part of CodeCordon's deterministic static-analysis pass. When it matches, the finding includes the source file, line number, severity, explanation, and a redacted snippet so the developer can inspect the evidence directly.
Recommended remediation
Proxy all LLM calls through your own server route. Keep the API key server-side; add per-user rate limits on the proxy.
How to use this result
- 1. Open the reported line. Confirm the match is active application code rather than a fixture, example, or false positive.
- 2. Apply the remediation in context. Preserve the intended behavior while removing the dangerous pattern.
- 3. Scan again. Verify the known pattern no longer appears, then continue with tests and any runtime or human security review appropriate to the application.
Limits of this check
A match is a review signal, not proof of exploitability. No match means only that this specific known pattern was not found in the applicable files. It does not rule out equivalent code, business-logic flaws, runtime vulnerabilities, or novel attack paths.