policy-as-code-linter

When to invoke

• Your org stores lightweight access/control policies as code (e.g., allow/deny rules).
• You want a quick lint pass to catch missing fields, invalid enums, overly-broad principals, or risky wildcards.
• You need vendor-neutral checks before deploying to any policy engine.

Inputs needed

• Path to a YAML policy file containing a list of rules.
• (Optional) Output path for a JSON report.