security-reviewer

To review source code for security vulnerabilities, use AI-assisted manual analysis to examine authentication, authorization, and input handling, targeting complex business logic flaws and IDOR that automated SAST tools often miss.

Yes, you can prioritize your security code review by providing optional context like sast_findings and endpoint_inventory. This tailors the AI analysis to focus on high-risk areas and specific framework misconfigurations.

The best way to find authorization misconfigurations is performing an AI-assisted manual review that traces data flows and input handling across your source files, producing structured findings with actionable recommendations and evidence snippets.

AI-assisted security analysis works for common programming languages and frameworks by applying provided language context to tailor checks. It examines source files and project configurations to identify risky patterns specific to your stack.

To start an AI-assisted security code review, provide the root path of your codebase along with optional context like sast_findings or endpoint_inventory to tailor the analysis. The tool then examines source files for vulnerabilities.

You should use a manual-style AI review instead of automated SAST tools to detect complex injection patterns, IDOR, and business logic flaws that automated scanners frequently miss, pairing human judgement with AI analysis for comprehensive coverage.