Security Code Review Prompt

Examine this Security Code Review case before constructing Security Code Review Prompt.

## Details to use for Security Code Review
- [CODE]
- [LANGUAGE_AND_RUNTIME]
- [TRUST_BOUNDARIES]
- [DATA_CLASSIFICATION]
- [THREAT_MODEL]

## Decision path for Security Code Review
1. Map entry points and trust boundaries.
2. Trace untrusted data through sensitive operations.
3. Rank exploitable findings separately from defensive hardening.
Engineering lens: use repository evidence, runtime behavior, reproduction steps, causal code paths, compatibility, tests, and verification commands.

## Result set for Security Code Review
- **Risk-ranked finding — Security Code Review result.**
- **Evidence in code — Security Code Review result.**
- **Abuse scenario — Security Code Review result.**
- **Minimal patch — Security Code Review result.**
- **Security regression test — Security Code Review result.**

## Human-review gate for Security Code Review
Every Security Code Review finding needs cited evidence, a consistent criterion, a severity, and a verifiable disposition.
Keep assumptions visible and refuse to turn them into facts.