This started as a small experiment and turned into a much bigger project than I expected. The tool is called git-archaeologist. It reads git history and tries to answer questions like: What parts of the codebase depend on one person? Has that person actually been active recently? Which areas are accumulating maintenance risk? Which files tend to break together? Where is knowledge becoming concentrated? One thing I learned while building it: The scary code isn't always the c...