security-audit

To audit codebases for security vulnerabilities, run a full-mode security audit that scans directories like src/, assets/, and config files across six categories, then outputs a prioritized remediation plan and Markdown report to production/security/.

Scanning game code for input validation and network security risks is done by running the targeted network or input audit modes, which analyze implementation gates and data exposure surfaces to identify misconfigurations specific to game security requirements.

Yes, you can generate a compliance-ready security report by running the audit workflow, which produces a structured inventory of risks and a dated Markdown file in production/security/ for gating and compliance reviews.

The security audit supports full, network, save, input, and quick scanning modes, allowing you to target specific vulnerability categories or perform rapid checks across design, implementation, and deployment phases.

A security audit identifies dependency risks and data exposure by applying a six-category systematic review across deployment gates, scanning relevant project files to detect leakage risks and misconfigurations before game release.

You need a full security audit for comprehensive pre-release checks across all categories, whereas a quick scan mode is suited for rapid, targeted vulnerability checks on specific areas like input validation or save files during active development.