I built a dead code forensics CLI because "this file is unused" is never enough (opens in new tab)

Every senior developer has stared at a file and thought: should I delete this? You run vulture. You run deadcode. They both tell you the file has zero import sites. You hover over the delete key. And then you don't delete it. Because you don't actually know why it's there. The real question isn't "is it dead?" — it's "why is it dead?" Dead code falls into very different categories: Category A — Accidentally orphaned. A file that got left behind when the calling code was removed. Safe to delet...