compliance-audit

Static regulatory auditing identifies and reports GDPR compliance gaps by scanning API routes, data models, privacy artifacts, and logging. It surfaces mechanical findings in data handling, consent, retention, and third-party processing without modifying code or live systems.

Static compliance analysis is a technique that scans source code to identify regulatory gaps without executing the application. It validates data handling, consent flows, and retention declarations against framework profiles like GDPR to produce structured, backlog-ready findings.

You can audit SOC2 or HIPAA readiness using profile scaffolding included in the skill. While the active scanning profile currently focuses on GDPR checks, SOC2 and HIPAA scaffolds are provided to guide future enablement and consistency.

Generate backlog-ready remediation entries by running a static compliance audit that produces structured findings with severity and readiness tiers. This output supports governance planning by surfacing missing endpoints, consent artifacts, and data retention statements for remediation.

Static regulatory auditing does not modify code or live systems. It performs read-only analysis of codebases to identify and report GDPR compliance gaps, returning structured findings without altering any project modules or services.

A GDPR profile check validates rights, consent, security measures, and accountability across API routes, data models, privacy artifacts, and logging. It applies to any project module or service by scanning for mechanical compliance findings.