This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Repo Salvage
Good code deserves a second life.
Repo Salvage helps developers and coding agents discover reusable parts, inspect commit-pinned source, and keep notices, dependency context and integration gaps together. Free MIT source with a local web app, read-only CLI and MCP adapter. Working prototype: start with the included examples; no hosted catalog yet.
A project can end while some of its code still has a future. Repo Salvage helps developers and coding agents find those useful parts and carry the context along: pinned source, discovered notices, dependency notes and integration gaps.
This is a working development prototype, free under MIT. The v0.2.1 developer release includes source, CLI/MCP archives, five worked-example bundles and checksums: https://github.com/seanebones-la...
With Node.js 22, download/extract the source, run npm ci, then npm run demo. Open http://127.0.0.1:3187/examples. This local demo needs no account or API key; sign-in and paid analysis are disabled, and its temporary data is separate from your normal installation. Start with the parser example, download its standalone adaptation, and run its consumer tests in a separate folder.
The agent API, read-only CLI and local MCP adapter support source inspection and fetching without a paid model request. Author analysis is a separate, optional provider-backed workflow.
A generated brief is a starting point for inspection. An owner review applies to its analyzed source commit. Neither one proves an extraction will work in your project. Read file notices, review dependencies and test your adaptation.
There is no public hosted catalog or npm registry release yet. Our recorded trials are controlled examples; independent usefulness, repeat use and marketplace demand remain open questions.
The short captioned overview shows real local screens and an included consumer check. I'd welcome feedback from developers who already have a small utility to find or a useful implementation to preserve.
Built by NextEleven.
About Repo Salvage on Product Hunt
“Good code deserves a second life.”
Repo Salvage was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #9 on the daily leaderboard. Repo Salvage helps developers and coding agents discover reusable parts, inspect commit-pinned source, and keep notices, dependency context and integration gaps together. Free MIT source with a local web app, read-only CLI and MCP adapter. Working prototype: start with the included examples; no hosted catalog yet.
On the analytics side, Repo Salvage competes within Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1M followers on Product Hunt. The dashboard above tracks how Repo Salvage performed against the three products that launched closest to it on the same day.
Who hunted Repo Salvage?
Repo Salvage was hunted by Sean McDonnell. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Repo Salvage including community comment highlights and product details, visit the product overview.
Sean McDonnell
Hi, I'm Sean, the builder behind NextEleven.
A project can end while some of its code still has a future. Repo Salvage helps developers and coding agents find those useful parts and carry the context along: pinned source, discovered notices, dependency notes and integration gaps.
This is a working development prototype, free under MIT. The v0.2.1 developer release includes source, CLI/MCP archives, five worked-example bundles and checksums:
https://github.com/seanebones-la...
With Node.js 22, download/extract the source, run npm ci, then npm run demo. Open http://127.0.0.1:3187/examples. This local demo needs no account or API key; sign-in and paid analysis are disabled, and its temporary data is separate from your normal installation. Start with the parser example, download its standalone adaptation, and run its consumer tests in a separate folder.
The agent API, read-only CLI and local MCP adapter support source inspection and fetching without a paid model request. Author analysis is a separate, optional provider-backed workflow.
A generated brief is a starting point for inspection. An owner review applies to its analyzed source commit. Neither one proves an extraction will work in your project. Read file notices, review dependencies and test your adaptation.
There is no public hosted catalog or npm registry release yet. Our recorded trials are controlled examples; independent usefulness, repeat use and marketplace demand remain open questions.
The short captioned overview shows real local screens and an included consumer check. I'd welcome feedback from developers who already have a small utility to find or a useful implementation to preserve.
Built by NextEleven.