# How to find active decompilation projects

Author: DecompHub
Updated: 2026-10-10
Language: en
Canonical: https://decomphub.com/guides/finding-active-decompilation-projects

To find an active decompilation project, combine repository activity with evidence that the work you care about is moving. A recent commit, a new release and a fresh progress report are different signals. None alone promises that someone will review your contribution.

## Read activity in context

Start with [DecompHub's activity sort](https://app.decomphub.com/explore?sort=active), then open the upstream repository. Check what recent changes actually concern: reconstructed code, build tools, documentation, automated maintenance or a downstream port. A date tells you when something changed; its content tells you whether that change is relevant to your goal.

GitHub's [search reference](https://docs.github.com/en/search-github/searching-on-github/searching-for-repositories) documents `pushed:` and `archived:` filters. Try [`decompilation pushed:>=2026-01-01 archived:false`](https://github.com/search?q=decompilation+pushed%3A%3E%3D2026-01-01+archived%3Afalse&type=repositories), replacing the date with a useful window for your search. This is a discovery filter, not a definition of project health.

## Check three separate timelines

- **Repository:** When did relevant code or documentation change? Which branch does the evidence concern?
- **Progress report:** What metric and build are measured, and is its date supplied by the publisher or merely when a directory read it?
- **Contribution process:** Are the instructions current, and is there a documented route for the kind of change you want to make?

Avoid turning a quiet month into an “abandoned” label. A project may be complete for one target, maintained infrequently or continued elsewhere. Follow any archived-repository or migration notice to its stated successor instead of guessing from its age.

## Verify progress before repeating it

Open the report linked beside a progress bar. Compare the same build, unit and scope across observations. A growing count with a changing denominator needs explanation; an unchanged bar does not prove no useful work happened. The [progress guide](/guides/understanding-decompilation-progress) explains those distinctions.

Keep a shortlist with a checked date and one observed fact per project, such as “the documented build procedure was updated.” Avoid unsupported labels like “most active” unless you define and measure the comparison. Use [the GitHub guide](/guides/finding-decompilation-projects-on-github) to expand the search when the first results do not fit.