REPOSITORY ANALYSIS, WITH A POINT OF VIEW
Measure one revision.Understand what matters.Trace every result.
Metrolith turns a repository revision into inspectable evidence — from structure and complexity to change, policy and provenance. Without collapsing it into a score.
See what Metrolith revealsFirst, see what’s really there.
A repository is more than a tree of files.
Bring its shape into focus, one layer at a time.
From observation
to your next question.
The useful part is what you can ask next.
No leaderboard. No universal quality score.
Callable complexity · Lexical & structural duplication · Maintenance attention · Changed code · Policy · Ratchet · Trace & provenance
This is what
your run becomes.
Measurements in context. Room to investigate.
A path from every displayed result to its evidence.
You’re seeing only the beginning.
The recorded Run Story continues through seven chapters before opening into the full Explorer.Point Metrolith
at a repository.
Public GitHub repositories only. Hosted service limits apply. Results expire after 24 hours.
A clear path.
An inspectable result.
One engine. Run locally or in the browser.
Inspect evidence for one exact revision.
- 01
Repository
Choose the source
- 02
Exact revision
Resolve the source state
- 03
Measure
Source, structure
and callables - 04
Investigate
Complexity, repetition
↳ Committed history, when needed
and selected analyses - 05
Explorer
Inspect results
and Trace
Start where
your code lives.
Keep source local. Ask the same questions.