LegacyLens
Read the code nobody documented.
Drop it on a codebase whose authors have all left. Get the module map, the hidden coupling, the parts that are load-bearing and the parts that are just scary — before you promise anyone a delivery date.
- built for
- Consultancies
- New joiners
- Due-diligence teams
- Migration leads
Why this exists
Why LegacyLens exists
There is a specific kind of dread that comes from opening a repository where every file’s last meaningful commit predates everyone currently employed.
The code works. That is the problem — it works for reasons nobody can articulate, so every change is a coin flip and every estimate is a guess dressed as a number.
LegacyLens exists to convert that dread into a map. Not a rewrite plan, not a quality score: a map of what is load-bearing, what is coupled to what, and which corners you can safely ignore until the third sprint.
Capabilities
What it actually does.
Load-bearing analysis
Which modules everything quietly depends on, ranked by how much of the system stops if you touch them.
Implied contracts
The undocumented assumptions between modules, recovered from call patterns and the shape of the data actually flowing through them.
Change-risk heatmap
Churn crossed with coupling crossed with test coverage. The red squares are where estimates go to die.
Under the hood
Specifications.
- Status
- Incubating — early access waitlist
- Languages
- TypeScript · Python · Java · C# (planned)
- Runs
- Fully local
- Target
- Q4 2026
Questions
The ones people actually ask.
Does the code leave my machine?
No. LegacyLens is designed to run entirely locally, because the codebases that most need it are exactly the ones whose owners will never approve an upload.