security-review

A security code review identifies exploitable vulnerabilities by researching the codebase before reporting, focusing on high-confidence findings like injection, XSS, and authentication issues. It outputs a structured, confidence-based vulnerability report with actionable remediation guidance.

Code security analysis detects high-confidence vulnerabilities including injection, cross-site scripting (XSS), authentication flaws, authorization bypasses, cryptography issues, and misconfigurations across multiple languages and frameworks.

Yes, this security review approach applies to code review tasks across all languages and frameworks, systematically detecting input validation, authentication, and cryptography issues using OWASP Cheat Sheets as a guide.

The best way to report code vulnerabilities is by generating a confidence-based vulnerability report that includes researched findings and specific remediation guidance, ensuring only high-confidence security issues are documented.

Use OWASP Cheat Sheets and embedded references to guide a systematic security review, researching the codebase to assess risk and identify high-confidence vulnerabilities like injection and authorization failures.

Security reviews often report low-confidence false positives when the codebase is not thoroughly researched before reporting. Enforcing research prior to reporting ensures only high-confidence vulnerabilities are identified, reducing noise.