I built a coroner for dead software. It issues death certificates, and it refuses to lie.

Description and use

Autopsy of a Dead Project automatically classifies GitHub repositories, determines their status (alive, abandoned, burned_out, etc.), and issues a death certificate with evidence-based causes of death.

Problem

Developers accumulate abandoned GitHub repositories that remain unacknowledged, creating a digital graveyard.

Outcome

The tool provides transparent, reproducible verdicts on repository health, distinguishing alive, abandoned, burned_out, completed, pivoted, and insufficient_history states, and outputs a death certificate grounded in measurable metrics.

Workflow

• Paste a GitHub repo URL into the web interface.
• The app extracts six numeric features from the GitHub API.
• TabPFN classifies the repo into one of five death modes.
• If needed, a deepseek-v4.1-flash LLM reads commit messages and README to refine the verdict.
• The app generates a grounded eulogy and a death certificate.
• The certificate is displayed to the user.
• The user can download or share the certificate.
• The tool caches results for quick repeat queries.

Evidence

Autopsy of a Dead Project is a forensic pathology tool for software. You paste a GitHub URL, and a machine examines the body, says plainly what the project was, works out how it died, and issues a death certificate

Source

TabPFN, leave-one-out: 58.1%

Source

The reader and the voice is deepseek-v4.1-flash, an open-weight LLM I run through 0G Compute

Source