omk-security-review

Reviewing code changes for secret exposure and injection risks involves analyzing workflow modifications to flag credential leaks, SQL injection, and command injection, then producing a structured security verdict with prioritized fixes.

A security review for protected files and dependencies evaluates modifications to sensitive files and package configurations to identify insecure usage, enforce sensitivity rules, and detect over-broad permissions that expand attack surface.

Checking deployment workflows for broken authorization and command injection requires evaluating shell commands and deployment steps for dangerous permissions and unsafe inputs, then enforcing protected-file sensitivity to prevent unauthorized access.

Automated security checks on file upload and API changes detect XSS, CSRF, unsafe path handling, and broken authorization, generating a critical-to-low security verdict with required fixes.

Dependency risk review covers insecure usage and over-broad permissions by evaluating package configurations, flagging dangerous shell and deployment steps, and enforcing protected-file sensitivity to harden code.

A secrets and injection security review is needed when modifying authentication, APIs, database queries, shell commands, or file uploads to prevent credential exposure, injection attacks, and authorization weaknesses before shipping code.