hook-enforcement-audit

To audit Claude Code hooks for enforcement gaps, analyze settings.json entries and registered hook files to classify authority levels, distinguishing hard block behavior from advisory-only configurations. The audit generates findings tables with prioritized remediation steps to restore enforcement coverage.

Hard block hooks actively prevent operations, while advisory hooks only warn or flag without stopping execution. The hook-enforcement audit classifies each hook's authority by analyzing settings.json and hook files to surface where infrastructure was deliberately softened to advisory-only.

Check compliance state receipts by analyzing state files like masonry-state.json within your Claude Code deployment. The audit examines receipt patterns to determine if compliance tracking is active or stale, identifying gaps in enforcement coverage.

Yes, the hook audit applies to Claude Code deployments relying on settings.json and hook .js files. It is designed for developers auditing security, config managers, and platform operators seeking to verify enforcement coverage and identify advisory-only gaps.

Remediate hook enforcement gaps by following the prioritized remediation steps generated by the audit. The audit produces deployment prerequisites and enablement guidance for enforcement flags when prerequisites are met, ensuring advisory hooks transition to hard block enforcement.