find-bugs

To scan local Git branch changes for security vulnerabilities and bugs, the Skill analyzes code changes against a comprehensive checklist covering injection, XSS, CSRF, race conditions, and cryptography, prioritizing the most critical findings for your review.

A security code review checklist covers injection, XSS, authentication, authorization, CSRF, race conditions, session management, cryptography, information disclosure, DoS, and business logic flaws, systematically verifying each area within the current branch changes to ensure adherence to best practices.

Yes, you can run an automated security audit on your code before a merge by scanning the current branch for common flaws. This process maps the attack surface by identifying areas handling user input and database interactions, then applies a security checklist to detect vulnerabilities.

Vulnerability scanning handles authentication and authorization logic by analyzing these specific operations within the code changes, verifying them against a security checklist to detect potential bypasses, broken access controls, and session management flaws, ultimately prioritizing any critical findings.

The best way to identify race conditions and business logic flaws in a new feature is to scan the local branch code changes using an automated checklist that specifically targets these concurrency and logic vulnerabilities alongside standard injection and XSS checks, effectively prioritizing critical results.