security-review

To audit your codebase for OWASP Top 10 vulnerabilities, you need a security review process that checks for broken access control, injection risks, insecure design, and misconfiguration. This Skill automates that process by analyzing your repositories and returning a structured report with severity levels, file locations, and remediation guidance.

Detecting hardcoded secrets and credentials requires scanning your codebase for exposed sensitive patterns. This Skill performs secrets detection across your repositories and modules, identifying exposed credentials before they become production incidents and providing specific file locations for remediation.

Checking project dependencies for known package vulnerabilities involves running a dependency vulnerability scanning process on your modules. This Skill scans your dependencies during feature development and pre-deployment checks to identify known package vulnerabilities that could weaken your system's security posture.

Yes, you can review authorization and input handling logic for security flaws after adding new API endpoints. This Skill performs input and authorization review specifically suited for use cases like new API endpoints, user-input handling, and authentication logic changes, producing a structured security report with severity and remediation guidance.

You should run a security audit on your repository during feature development, after API changes, and during pre-deployment checks. Running a security review at these stages helps identify injection risks, broken access control, and SSRF vulnerabilities before they reach production environments.

Yes, this security review approach covers SSRF and insecure design misconfigurations as part of its OWASP-focused auditing. It checks code for broken access control, injection risks, insecure design, misconfiguration, and SSRF, providing comprehensive vulnerability detection across your repositories and modules.