GitHub Insights
GitHub Insights
Role
Every public family repo gets free native code stats from GitHub:
- Contributors graph — per-author commits over the lifetime of the repo
- Commit activity — last-52-week heatmap
- Code frequency — additions/deletions per week
- Network + forks — fork tree
- Dependents — packages depending on this one (if it's a public package)
- Traffic (private to the owner) — clones + visitor counts + popular content + referrers, last 14 days
No setup — Insights is on by default for every public repo. The
family /stats page reads these via the REST API at build time per
family-wide-stats-page.
Free tier
Free, unlimited, native to every public GitHub repo. No quota.
Card / subscription required?
NO. Native to every GitHub account.
Alternatives
- Tokei — sibling tool in this stack, complementary: Tokei does per-language line counts, GitHub Insights covers commits / contributors / activity over time. Both feed the family /stats page.
- Code Climate Quality — overlap on maintainability dashboards but Insights is the canonical authorship + cadence source.
- Self-hosted git stats (gitstats / git-quick-stats) — same data recomputable locally; redundant when GitHub already exposes it via free API.
Swap cost
Zero — GitHub Insights is a property of hosting on GitHub. If the family ever moved off GitHub (it won't — GitHub Issues only
- GitHub Projects only
- GitHub Pages mirror are all locked), equivalent stats would have to
be regenerated from
git log.
Why this is our pick
The 9-tool code-stats stack (decision) deliberately includes every metric the family can auto-track for free. GitHub Insights is the native code-stats layer — already running, already covering every repo, already free. Including it as a documented service makes the family-wide /stats page an explicit consumer instead of an implicit one.
Auto-tracked end-to-end: GitHub computes every graph from git log
itself, no human action triggers updates. Aligns with the
auto-only-tracking rule.