spectra-audit

You can audit git diff for security vulnerabilities by running a static analysis on the current code changes to surface dangerous defaults, type confusion, and silent failures. This process targets security sharp edges introduced in your latest commits.

Static analysis for dangerous defaults and silent failures is an automated code review process that identifies insecure configurations and hidden error paths. It enforces secure-by-default principles by surfacing type confusion and silent failure risks before deployment.

Yes, you can integrate security audits into your dev-ops workflow using Discipline mode, which runs integrated checks during implementation. This enforces continuous risk management and secure-by-default practices directly within your code review process.

The best way to review code changes for type confusion risks is using a triad assessment framework that evaluates code from Scoundrel, Lazy Developer, and Confused Developer perspectives. This multi-agent parallel analysis surfaces hidden security vulnerabilities.

The security audit operates on the current full git diff in Standalone mode, performing a 3-agent parallel analysis across all changed code. This ensures comprehensive risk management coverage for your entire code changeset.

You should reconsider automated code review for security risks when your changeset is empty or when you need runtime dynamic analysis rather than static-analysis. The audit specifically targets static security sharp edges in changed code, not runtime behavior.