lazarus
Recovers value from abandoned research codebases by converting them into reusable, production-ready pipeline components, reducing redundant development effor…
An agent that takes a dead research repo and turns it into a callable pipeline component.
- Ask Claude to revive an abandoned research repository into a working pipeline module.
- Automate conversion of legacy research code into reusable infrastructure components.
- Generate documentation and interfaces for old research projects to integrate with pipelines.
Recovers value from abandoned research codebases by converting them into reusable, production-ready pipeline components, reducing redundant development effort and accelerating time-to-deployment for experimental features.
Platform engineering teams and ML ops teams integrating research outputs into production data or ML pipelines.
https://github.com/DoctorDean/lazarus
By DoctorDean
How to Get It
claude plugins install DoctorDean/lazarus
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Revive an abandoned research repository into a working pipeline module
Trust Signals Auto-scanned
Community Pulse New
- Amazon developing three new sci-fi series: Lazarus, Snow Crash and Ringworld — Hacker News · 293 pts
- Lazarus Release 4.0 — Hacker News · 276 pts
- Lazarus Group laundered $200M from 25 crypto hacks to fiat — Hacker News · 268 pts
3 mentions across 1 sources
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 48 GitHub stars; contributors unknown; last commit 2d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 48 GitHub stars; contributors unknown; last commit 2d ago; license MIT.