Hey Product Hunt, I built graveyard because dead code cleanup gets awkward fast in mixed-language repos. Python has one tool, JS/TS has another, Rust has another, and none of them share a ranking model or an easy CI adoption path. I wanted one workflow that could scan a repo once across Python, JS/TS, Go, and Rust, then help teams focus on what actually looks stale instead of dumping noisy results. That led to graveyard: git-aware confidence scoring, baseline save/diff for CI ratchets, and JSON/CSV/SARIF output for automation and code scanning. The wedge is not “replace every dead-code tool.” If a repo is single-language, a focused tool can still be the right answer. graveyard is for mixed-language repos where the team wants one dead-code workflow. Would love feedback on where this feels useful or wrong, especially scoring, false positives, and language gaps.

Graveyard

One dead-code scanner for mixed-language repos

One dead-code scanner for mixed-language repos