Module top_committers 

top-committers analysis — per-author commit leaderboard.

What this signal tells you

For each canonical author (post-mailmap), this analysis emits a global summary of their contribution: total commits, total lines added/deleted, and the first and last commit dates. It’s the answer to “who’s the biggest contributor by raw commit count” — useful for release-notes generation, contributor-recognition snapshots, velocity dashboards, and onboarding (who should I ask about this codebase as a whole?).

Relationship to the authors analysis

This is a DIFFERENT analysis than authors. authors answers a per-file question (“how many distinct contributors touched this module?”, Bird et al. 2011 defect-risk indicator). top-committers answers a global per-author question (“who has the most commits repo-wide?”, contributor-leaderboard signal).

In code-maat, the per-file question is -a authors. There’s no built-in per-author leaderboard — users approximate it by running -a author-churn and sorting. CodeLore exposes both as first-class named analyses so the operator picks the question, not the workaround.

Columns (richer than the approximate code-maat workaround)

• author — canonical email (post-mailmap, post-bot-filter).
• commits — distinct commits attributed to this author.
• loc_added — total LoC added across all commits.
• loc_deleted — total LoC deleted across all commits.
• first_commit — calendar date of this author’s earliest commit.
• last_commit — calendar date of this author’s latest commit.
• is_bot — flag from author_aliases.is_bot. Surfaces Dependabot / renovate / similar bots so dashboards can suppress or visually distinguish them without joining a second table.

Research basis: see docs/research-foundations.md entry “top-committers”.

Structs

TopCommittersRow

Functions

run_top_committers