SPB Git

about · metrics

How the numbers are counted

Every statistic on SPB Git is computed from the bare repositories on disk. Nothing is estimated or sampled. This page states each definition so that two numbers that look comparable really are.

Commits

  • Commits (per repository) — git rev-list --count HEAD: every commit reachable from the default branch, including merges. Commits that only exist on other branches are not counted.
  • Commits, all time — the sum of the per-repository counts above across all 171 repositories.
  • Commits, last 52 weeks — the same commits (default branch, every repository), kept when their committer date falls inside the 52-week calendar grid ending today (UTC days, weeks start on Sunday). Because it is a filter of the all-time set, it can never exceed the all-time total.
  • Both figures come from one pass over the repositories and are recomputed together whenever a push changes any default branch; a repository pushed while the server was unavailable is detected on the next request by comparing the cached HEAD with the live one.
  • Identity rule: a commit is counted once per repository where it is reachable. Mirrors or forks of the same history therefore count their commits again — this is deliberate (the catalog counts repositories, not unique commits).

Calendar, streaks, active days

  • Calendar cell — commits whose committer date (UTC) falls on that day. Colour levels are quartiles of the busiest day in the window.
  • Active days — days with at least one commit in the window.
  • Day streak — consecutive active days ending today; today may still be empty without breaking the streak.
  • Longest streak — the longest run of consecutive active days inside the window.
  • Sparkline (repository cards) — weekly commit counts over the last 26 weeks, same source.

Languages

  • Repository language bar — bytes per language at HEAD, Linguist-style: only programming and markup languages, vendored paths and lock files excluded.
  • Languages (site) — number of distinct languages appearing in at least one repository bar.
  • Stack ring — each repository contributes its percentage split with equal weight, so a single large repository cannot dominate.

Activity, clones, size

  • Last push — the most recent committer date across the repository's branches.
  • Activity feed — events recorded by the post-receive hook (pushes, tags, deletions).
  • Clone count — number of git-upload-pack requests (clones and fetches, including CI and crawlers). Shown only when non-zero.
  • Size on disk — loose plus packed object size reported by git count-objects.
Menu

Theme