Code forensics report
Repository evidence overview
Mischief. Mayhem. Merge conflicts. Exposed.
Evidence, not a verdict
Signals remain separate and their supporting counts stay visible.
What to do next
Investigation leads
Evidence-backed starting points, not automated conclusions.
Files ranked by hotspot evidence
0 matching files · select one to inspect
Sort with column headers. Use Tab then Enter on Inspect.
Change landscape
Grouped by code area. Tile area compresses lines changed to keep smaller files visible. Colour is hotspot rank.
Change frequency × complexity
Upper-right files combine repeated change with difficult code.
Confidence-first temporal coupling
Support comes before a flattering percentage. Both revision counts remain visible.
How to read this: raw ratio is shared revisions ÷ the smaller file revision count.
The 95% Wilson lower bound discounts perfect-looking results with tiny samples.
Collection state
CI evidence
Observed failures
Failed workflow runs
Recovered retries
Flaky steps
Interpretation