security-detection

To detect security-critical changes in staged git files, run the detection script using either Python with the --git-staged flag or PowerShell with the -UseGitStaged parameter. It scans staged modifications against defined critical and high-risk patterns to produce clear risk signals for security review.

Yes, you can scan specific configuration and CI/CD files for security risks by passing explicit file paths directly to the detection script. This direct file analysis identifies critical and high-risk changes without requiring a git staging step.

Security-critical change detection for code review is the process of scanning code, configuration, and CI/CD files against defined high-risk patterns. It identifies sensitive modifications to trigger security agent review recommendations and ensure proper security oversight.

No, this security detection tool has minimal dependencies and requires no external packages. It relies on built-in Python or PowerShell environments to execute cross-platform file scanning and risk detection.

During infrastructure security scanning, high-risk files include modifications to code, configuration files, and CI/CD pipelines. The tool analyzes these file sets against defined critical patterns to determine security risk and trigger reviews.

You trigger a security review for sensitive infrastructure modifications by running the detection script on git-staged changes or explicit file lists. The scan produces clear risk signals that drive security agent review recommendations and remediation actions.