security-guardian

To audit generated code for security vulnerabilities and secrets, you need an automated scanning mechanism that identifies insecure patterns, misconfigurations, and exposed credentials. This system provides structured findings with clear remediation steps without auto-fixing, requiring user approval for changes.

A zero-trust security review of cross-skill references involves validating consistency and enforcing strict access defaults across all workspace artifacts. It checks new or updated configurations and code to ensure no insecure patterns pass through the workspace without explicit approval.

To check for exposed environment variables before deploying code, scan the deployment artifacts and configuration files for secrets. The audit identifies potential insecure patterns and misconfigurations, providing structured findings with remediation steps rather than auto-fixing the issues.

No, you cannot use this security audit to automatically fix insecure patterns. It identifies and reports vulnerabilities across code, artifacts, and configurations, providing structured findings with remediation steps, but requires explicit user approval for any changes.

You need a security audit for workspace artifacts and configurations whenever new code, updated skills, or environment variables are introduced. This catches vulnerabilities and misconfigurations before they reach production or get stored anywhere in the workspace.