security-audit

To run a read-only security audit, execute the skill against your local repository to surface findings across four domains without modifying any code. It analyzes your codebase and produces a structured findings report for architects to review.

The best way to check for secrets and supply chain risks is using a domain-based security audit that scans your local repository. This process evaluates your codebase against a domain checklist to identify exposed secrets and dependency vulnerabilities.

No, this security audit tool does not modify your codebase during analysis. It performs a strictly read-only review of the repository to surface security findings without making any changes to your files.

Yes, you can use this audit for OWASP Top 10 compliance checks before deployment. It is specifically designed for pre-release reviews, risk assessments, and compliance readiness by analyzing your local repository against a domain checklist.

A domain checklist works for CI/CD security assessments by systematically evaluating your pipeline configuration against known security criteria. The audit uses this checklist to identify misconfigurations and vulnerabilities across your CI/CD domain.