validator

To verify audit findings, provide a structured list of findings with exact file paths and line ranges. The validator reads the cited code and surrounding context to return a VERIFIED, FALSE_POSITIVE, or NEEDS_CONTEXT verdict with a concise rationale.

Filtering false positives from static analysis reports involves cross-checking cited guard clauses or defensive logic to confirm context. The validator evaluates each finding at its file location to output a verdict and rationale, streamlining post-audit validation.

Yes, you can use the validator to check findings across multiple repositories. Its scope covers post-audit validation across repositories, focusing on specific findings that require confirmation by reading the cited file paths and surrounding context.

The NEEDS_CONTEXT verdict during code verification indicates that the validator cannot definitively confirm or reject the reported issue based on the cited file and surrounding context alone. It outputs this verdict alongside a concise rationale explaining the missing information.

You need post-audit validation for your codebase when you have a static analysis report with specific findings that require confirmation. The validator ensures audit credibility by identifying whether cited code locations actually contain the reported issues, reducing false positives.

To start verifying static analysis findings, you should provide a structured list of findings with exact file paths and line ranges. The validator assesses each finding by evaluating the cited file and surrounding context to return a final verdict.