Secret exposed to the browser via public env prefix
An environment variable with a public client prefix (NEXT_PUBLIC_, VITE_, REACT_APP_, EXPO_PUBLIC_) has a secret-sounding name. These variables are inlined into the JavaScript bundle and readable by every visitor.
What the check contributes
Rule SEC004runs 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
Never put secrets in client-exposed env vars. Move the call that needs the secret to a server route/API handler and keep the key server-side only.
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.