audit

Running a repository audit scans your codebase, inventories test assets, and classifies app type to surface actionable test coverage findings. It outputs markdown reports, terminal banners, and JSON sidecars to highlight missing tests.

Scoring test readiness involves running an audit that classifies app type, applies tiering and context modifiers, and produces rationale-backed gap lists. It persists audit state and writes covered-surfaces.json for downstream security integration.

Yes, the audit supports both full-repo and scoped scans. It handles mixed-stack scenarios, enforces data contracts, and surfaces findings with context modifiers and denial trails to ensure accurate coverage assessment for the targeted scope.

Yes, the audit explicitly handles mixed-stack scenarios by enforcing data contracts and classifying context modifiers with grounded rationales. It inventories relevant test assets and configuration across different stacks to produce unified gap findings.

You get three output views: a markdown report, a terminal banner, and a JSON sidecar. The audit also writes a covered-surfaces.json file specifically for vibe-sec integration and persists the audit state for future reference.

A denial trail is produced to enforce data contracts and track excluded surfaces during the audit. It ensures transparency by logging why certain areas or test assets were denied coverage, providing grounded rationales for the final gap findings.