What problem does it solve? Audit findings observed at a point in time may already be fixed by later commits, but without aligning each finding's observation timestamp against the commit/deploy timeline you risk reporting resolved issues as open or missing still-broken ones. Timezone mismatches between UTC data timestamps and local git commit times silently flip verdicts. ## Core Features & Use Cases - Temporal verdict classification: Assigns each finding a verdict (STILL_LIVE, RESOLVED_DEPLOYED, RESOLVED_MID_WINDOW, PARTIAL, STALE_OBSERVATION_ONLY) based on first/last observation times versus fix commit times. - Timezone normalization: Converts git commit timestamps from the committer's local offset to UTC before any comparison, preventing the most common verdict-flipping error. - Mechanism verification: Reads the current code and diffs rather than trusting commit messages, confirming whether the buggy construct still exists at a specific path and line. - Use Case: Before finalizing a production audit, cross-check 30 flagged findings against git history and discover that 8 were already fixed by commits landing days after the observations, correcting the report before delivery. ## Quick Start Validate my audit findings list against the git history to determine which issues are still live and which were already fixed by recent commits.
