I built RepoSquirrel originally for myself as a team lead. I wanted a simple way to understand what’s actually happening across our repositories:

• Which repos and subsystems are actively developed? • Who is contributing where? • Who really knows a particular subsystem or owns most of the code? • Who is building competence in a repo or area? • What subsystems are not maintained or under-staffed? • How is the code evolving over time? • Does the team have enough capacity to maintain the products they’re responsible for? • What languages and technologies are used across the codebase?

I couldn’t find a tool that answered these questions without sending all our code to a third-party SaaS platform or locking us into GitHub/GitLab analytics. So I built RepoSquirrel.

RepoSquirrel is a local, self-hosted Git repository analytics and code ownership tool. It analyzes repos on your machine and generates dashboards showing:

• Subsystem ownership based on git blame/history • Contribution timelines by developer, team, or directory • Hotspots and churn over time • Orphaned / rarely touched areas of the code • Cross-repo analytics (who works where) • Language and technology breakdowns • Team maintenance load and competency patterns

My goal was to get visibility into knowledge distribution, bus factor risks, onboarding needs, and how engineering effort is spread across products.

Repo link: https://github.com/reposquirrel/reposquirrel

I’d appreciate feedback — especially from engineering managers, tech leads, and people working with multiple repos or large codebases. What insights would you want it to surface next?