WeWorkBuddy

Show HN: Unref – A Python dead code finder built on Ruff's parser

I wanted a good Python dead code finder that just works, with minimal config, until Ruff adds support for that ( https://github.com/astral-sh/ruff/issues/872 ). None of the newer alternatives to Vulture worked out of the box on my codebases, so I decided to build one. The first version was in Python, then I switched to Rust for speed and to reuse Ruff's parser. It checks all of CPython in under a second. It found lots of interesting dead code in my team's codebases, and it's the first time in ye

Read original source
Source reference for Show HN: Unref – A Python dead code finder built on Ruff's parser. Screenshot not yet available.
Source record · preview pending · news.ycombinator.comOpen the source for the full page.

Source record

Recorded metrics

points · 4 votes
2026-11-18 06:40:41.748Z
cumulative since publication

Research analysis

Project record

Repository: Apakottur/unref. Source account: I wanted a good Python dead code finder that just works, with minimal config, until Ruff adds support for that ( https://github.com/astral-sh/ruff/issues/872 ). None of the newer alternatives to Vulture worked out of the box on my codebases, so I decided to build one. The first version was in Python, then I switched to Rust for speed and to reuse Ruff's parser. It checks all of CPython in under a second. It found lots of interesting dead code in my team's codebases, and it's the first time in ye

Observed adoption & comparisons

Source votes: 4 votes (Nov 18, 2026 UTC; cumulative since publication) Recent records to compare: “interfere-inc/landmines” (Trendshift, Nov 18, 2026); “nexu-io/openmotion” (Trendshift, Nov 18, 2026). Shared themes are navigation hints; they have not been verified as the same need or independent corroboration.

Adoption decision

Evaluate it against the tool or manual workflow it would replace. The stored record supports discovery; it does not yet establish reliability, lower operating cost or commercial adoption.

Unverified requirements

Not verified: license permissions, required hardware, installation steps, maintenance status and a representative task with its failure cases.

Next test

Choose one real task and a current alternative. Record the commit, environment, input, output, elapsed time and failure behavior; retain the result before recommending adoption.