Git forensics for what is missing across rewritten history.
unconformity is a git forensics tool for what is missing: force-pushes, squash merges, deleted branches, rebases, and the history gaps they leave behind.
Treats missing commits and rewritten history as first-class evidence rather than anomalies to ignore once the branch looks clean again.
Useful when you need to understand what vanished from the visible graph and why a repository's present state no longer tells the full story.
Built for engineers who already live in git and want a sharper investigative lens instead of more dashboard noise.
The project has a memorable conceptual frame and a real technical target. It is not generic source control tooling; it is specifically about investigating absence and rewrite, which makes it stand out in the catalog.
If churnmap asks where code keeps changing, unconformity asks what disappeared from the story entirely. That makes it a natural companion to other code archaeology and QA-oriented entries in the relaunch.
Inspect a repository after rewritten history to identify what vanished, which commits were displaced, and where the visible graph stopped telling the whole story.
Use it when deleted branches, squash merges, or rebases complicate an audit trail and you need a more forensic view of how history changed.
The CLI-oriented repository is the right starting point if you want to study how unconformity reconstructs missing history and frames git rewrite events as evidence.
If the repository clicks for you, use the related projects below to trace how the same ideas show up in adjacent tools and experiments.
Skim the catalog when you want breadth, or use pages like this one when you want a little more context before heading outward.