I built Arbor to make sense of a GitHub repo
I built Arbor because reading a new codebase takes too long. You open a repo, click through folders, and still have no clear picture of how it all fits together. Arbor takes a GitHub repo and turns it into an architecture map, plus a health score across six areas: architecture, tech debt, performance, documentation, security, and design system. The map shows the structure. The score shows where…
We haven't written up this one. Dev.to has the full story — the link below goes straight to it.