Appearance
Contributors
This lens answers: who does the work, in which code, and who has stopped committing? It also shows how concentrated the work is and who is new.
It only sees commits in the analyzed period, which is the last 12 months by default. Someone who left before the period isn't listed at all, and "first commit" means first in the period. A status also says nothing about why someone stopped: they may have changed teams, moved to reviewing, or be on leave.
Reading the numbers
| What you see | What it means |
|---|---|
| active | Their last commit is less than 90 days before the newest commit in the analyzed period. On longer periods that grows: see the statuses. |
| quiet | Their last commit is between the active and gone cutoffs: 90 to 180 days before the newest commit on a short period. They worked here recently, and just haven't committed lately. |
| gone | Their last commit is more than 180 days before the newest commit on a short period, about six months on the default. It means no commits, not that they left. |
| "8 of 9 contributors are active" | How many people in the analyzed period are active now. The second number only counts people with a commit in the period. |
| "and 2 joined in the 90 days before the last commit" | People whose first commit in the analyzed period is in those 90 days. Someone coming back after a long break counts, and on a window of 90 days or less everyone does. |
| "The top 3 made 60% of the commits" | The three people with the most commits, as a share of all commits by people and AI agents. It's about commits only, not lines or knowledge. |
| "1 person made one" | People with exactly one commit in the period, usually drive-by fixes. |
| "1 bot with 50 commits is not counted" | Dependency and release bots aren't contributors, so they aren't in the people, the statuses, the top 3 or the package numbers. |
| "1 of the top 9 is gone: Marta Silva; 412 commits, and 38 files still theirs." | Gone people among the 10 with the most commits (fewer when the repository has fewer people). The commits are theirs in the period, and the files are the ones they still own. The 412 is what tells you whether this matters: on a repository with a long tail, "top 10" can be people with two commits. |
| "services/ledger: 87% of its 472 commits came from people no longer active." | At least half of the package's commits in the period came from quiet or gone people. There's no minimum size, so a package with one commit can say 100%. |
| "5 ghosts of 40" | The lens's reading on the Overview. A ghost is a gone person, the same count under another name. |
| Files owned | How many files they're the top committer of, which can be a low bar: one commit is enough for a file nobody else touched. |
| Lines changed | Lines added plus lines removed, across all their commits and every file those commits touch, lockfiles and generated files too. Binary files add nothing. |
| Active days | Distinct days with a commit, by the date in the author's own time zone. |
| Focus areas | Where most of their file changes are, up to three. |
The table's tiers are Active, Quiet, Gone and Gone, still owns files. They describe commit activity, not how anyone is doing their job.
Four example repositories
These repositories are invented, but each result is what GitRelic reports for commits like these.
A Go backend where one person moved on
1 of the top 9 is gone: Marta Silva; 412 commits, and 38 files still theirs.
services/ledger: 87% of its 472 commits came from people no longer active.
8 of 9 contributors are active, and 2 joined in the 90 days before the last commit. The top 3 made 60% of the commits; 1 person made one.
What it means: the team is mostly here, but one package was built mainly by someone who stopped committing to this repository about seven months before its newest commit. That's a question about the code, not about Marta. Someone else, with 60 commits, has been working on it since.
What to look at: Ownership shows whether services/ledger now rests on one person, Handoffs whether it changed hands, and Experts who to ask about it today. Marta may well still be around to ask: the lens only knows about commits.
A Python repo where many people went quiet at once
ml: 100% of its 430 commits came from people no longer active.
ingest: 79% of its 190 commits came from people no longer active.
3 of 7 contributors are active, and 1 joined in the 90 days before the last commit. The top 3 made 71% of the commits.
What it means: nobody is gone, which is why there's no "top 10" line, yet four people are quiet and two packages are flagged. Quiet is a recent state: these people all committed in the last six months, just not the last three. It might be a reorganization, a project that finished, or work moved to another repository.
What to look at: switch to Lanes. If those rows stop in the same few weeks, something happened to the group rather than to each person. Then ask whether ml is finished or waiting: Age shows how long it has been untouched. If you run this report again in a few months, anyone quiet who hasn't committed since will read as gone.
A Rust open-source project with a long tail
2 of the top 10 are gone: Lea Fox and Ada Kim; 5 commits between them, and 4 files still theirs.
docs: 100% of its 5 commits came from people no longer active.
16 of 54 contributors are active, and 12 joined in the 90 days before the last commit. The top 3 made 97% of the commits; 44 people made one.
What it means: every warning here is small. The "top 10" stops mattering after the third person: the top 3 made 1,850 of the 1,912 commits, and 5 commits say nothing about losing knowledge. The docs flag rests on the same 5. The low active count is the long tail too: someone who sent one fix eight months ago is correctly "gone," and that isn't a loss.
The number that matters is the 97%. Almost everything runs through three people.
What to look at: Ownership shows whether those three share packages or each hold their own. The 12 who joined are worth a look in the table too: they may be new, or back after a long break.
A TypeScript repo read over two windows
With the default 12 months:
1 of the top 4 is gone: Gil Marsh; 18 commits, and 18 files still theirs.
3 of 4 contributors are active, and 0 joined in the 90 days before the last commit. The top 3 made 95% of the commits.
The same repository with --since all, six years of history:
2 of the top 8 are gone: Max Weiss and Ty Cole; 370 commits between them, and 60 files still theirs.
5 of 8 contributors are active, and 0 joined in the 90 days before the last commit. The top 3 made 61% of the commits.
What it means: neither is wrong, but they aren't the same question. Gil Marsh last committed about eight months before the newest commit: gone on the default, where gone starts at six months, and active over six years, where active reaches back 550 days and gone starts past 1,100. The default run doesn't list Jo Bell at all, with 400 commits over the years and none in the last 12 months. And the 95% is mostly because only four people committed in the period.
What to look at: use the default for who is here now, and --since all for who built this. For a flat rule that doesn't stretch with the window, use "quiet" on Ownership: always 90 days.
How it's measured
GitRelic reads the commits in the analyzed period, leaves out merge commits, and builds one profile per person from the commits they authored. Being named in a Co-authored-by: trailer doesn't add a commit to anyone's count.
Who counts. People and AI agents. An AI agent's own commits make it a contributor like anyone else, so it can show as active and be in the top 3. Dependency and release bots don't count: addresses starting dependabot@, renovate@ or semantic-release@ (or those names with [bot], or semantic-release-bot@), github-actions[bot]@, and any other [bot]@*.noreply.github.com account that isn't an AI agent. See What counts as AI.
The statuses
A person's status comes from their last commit in the period, counted back from the newest commit in the period, not from today. That makes a report reproducible, and a report on an older checkout says what was true then. Dates are author dates.
The cutoffs depend on how long the analyzed commits span, from the first to the last. It's the span of the period, not the repository's age:
| Active cutoff | Gone cutoff | |
|---|---|---|
| Rule | The larger of 90 days and a quarter of the span | The larger of 180 days and half of the span |
| Default 12 months | About 90 days | About 180 days |
--since all, 2 years of history | 183 days | 365 days |
--since all, 6 years of history | About 550 days | About 1,100 days |
A last commit exactly on a cutoff reads as quiet.
"Quiet" means something else on other lenses. Ownership, Experts and Handoffs call someone quiet after 90 days without a commit, whatever the window. So anyone quiet or gone here is quiet there too. On a long window, someone active here can also be quiet there.
Files owned
The number of files where this person made the most commits in the period, with these rules:
- Every file has one owner, however close the race: someone with 34% of a file's commits can own it.
- There's no minimum: one commit is enough if nobody else touched the file.
- Only files that still exist in the analyzed commit count.
- Bots never own a file, and images, fonts and build output are never counted.
- Config files (manifests, lockfiles, changelogs, licenses, CI and tool configuration) don't count, and neither do fixtures and generated code, unless you pass
--include-fixtures, which brings back those two.
So this is "where they did the most," not "what rests on them." Ownership answers that one, per package.
Focus areas
A person's top three folders, by how many file changes they made in each. Each file in each commit counts once, so a commit changing ten files in one folder adds ten. A folder here is the first two levels of the path:
services/ledger/store/tx.gocounts towardservices/ledger.src/main.rscounts towardsrc/main.rs, since the first two levels are the file itself.- A file at the top of the repository counts toward the repository root, shown as
.in the table.
Unlike files owned, this counts every file, including deleted, config and generated ones.
Packages
The picture and its package numbers use the same packages as the rest of the dashboard: one of the repository's own declared workspaces, else packages/*, apps/*, libs/* or services/*, else the top-level folder. Files at the top of the repository are (root).
- A commit counts once in each package it touched, so a person's bands can add up to more than their commit count.
- A package's commits are every commit touching any of its files, config included, so its count can be higher than on Ownership, which leaves config out.
- Bot commits don't count, so a package only bots touch isn't in the picture.
Identity merging
Before any analysis, one person's addresses become one contributor. GitRelic applies the repository's .mailmap, and then merges:
- Addresses differing only in case.
- A GitHub noreply address and another address, when the noreply login matches exactly one person: the name part of their email, their full name without spaces, or a handle made from it (
msilvaormartasfor Marta Silva, six letters or more). - The same full name across addresses, when it has two or more words and isn't a placeholder like "root" or "Your Name."
AI agents and bots are never merged by name or login. The merged person takes their most-used name, and their most-used address that isn't a noreply one. Their card lists the others under Also commits as.
To join addresses these rules can't, add them to .mailmap, or keep the mapping out of the repository with git config mailmap.file ~/my-mailmap. To turn merging off, use --no-merge-identities.
In the dashboard
Find this lens under Team & Activity. Each status has its own color, which depends on your theme: active is the neutral one, and quiet and gone use the theme's two warning colors.
- The flow is the main picture. People are on the left, the 14 with the most commits, and everyone else shares an others node. Packages are on the right, the 11 with the most commits, and the rest share an other packages node. A band joins a person to a package, as wide as their commits touching it, in the person's status color. Bands from quiet and gone people are drawn stronger, because they show which code they left. A package sits level with the people who commit to it most. Its second line gives its commits and people, plus the share when it's flagged, which only these 11 can be. Hover a person or package to light their bands. Select a person and their bands take the accent, and the packages they never touched dim; select a package to do the same for its people. The others nodes can't be selected.
- Lanes (the corner toggle) has the same people as rows, with their commits per week, or per month when the period runs past two years, so arrivals and departures line up. Bars share one height scale, in the person's status color, with a last row for everyone else. A ruler under the rows shows where a last commit makes someone gone, quiet or active, with the dates. Anyone not active has an end mark at their last commit, where their row stops. The right side says each person's status and how long ago they last committed. Select a person by clicking anywhere on their row.
- Hovering a person shows their commits, status, last commit, the packages they commit to most and the files they own. A package shows its commits and people, its split across active, quiet and gone, and who committed most. A band shows the person, the package and the commits between them. A week's bar in Lanes shows its commits and the package most of them touched.
- The time strip under the picture shows each week's commits. With a selection, it shows the selection's.
- The inspector, with nothing selected, leads with how many are active and shows the findings quoted above, the five people with the most commits and their status, and a link to the table. Flagged packages appear in the findings once the commit history has loaded, up to two.
- A person's card adds the numbers above, how long ago their first and last commit were (counted back from the newest commit, not today), their weekly activity and their focus areas. When the data is there, it also shows packages they top and which would have nobody else if they left (from Ownership), handoffs, packages they're first to ask about, off-hours commits, and AI and co-author credits. Someone with no commit in the period, reached from Handoffs or Experts, says "none in this window."
- The table (
T) lists every contributor: status, commits, files owned, lines changed, first and last commit, and focus areas.
In the terminal, the Contributors panel lists the eight people with the most commits, a filled dot for active and a hollow one for quiet or gone, with their commits and top focus area.
What it can't tell you
- Why someone stopped. A gone person may have left the company, moved to another repository, or be reviewing every pull request. Nobody should be judged by this lens: it counts commits, and plenty of valuable work never becomes one.
- Who has really left, on a repository that stopped. Statuses count back from the newest commit, so a repository abandoned two years ago still shows active people on a
--since allrun. Check the last commit date first. A wrong clock works the other way: one commit dated in the future makes everyone else look like they've stopped. - Anything before the period. On the default, someone who wrote half the code 13 months ago isn't listed, and a long-time maintainer's "first commit" is 12 months ago.
--sincecounts from today, so an old checkout has fewer commits or none. Use--since allto look further back. - Who is new, on a short window. "Joined" means first commit in the period. Returning after a break counts, and with
--since "3 months ago"nearly everyone counts. - Work that isn't an authored commit. Merge commits are left out, so someone who only merges pull requests won't appear. In a squash merge, only the commit's author is counted, not a co-author in its trailer. See AI & Co-authors for those.
- Whether two addresses are one person. Merging is a best guess. One person under a nickname and a work address stays two people until you add them to
.mailmap. Two different people with the same full name become one;--no-merge-identitiesundoes that for the whole report. - Work on a file before it was renamed. Each commit counts under the path it changed, so someone's older work can sit under a path that no longer exists, and doesn't count toward files owned.
Related
- Ownership — how much of each package rests on one person. Files owned here is per file and has no minimum share; Ownership is per package.
- Experts — who to ask about a package today, over all of history.
- Handoffs — who took each package over from whom, and what nobody picked up.
- Ghost Files — files where one person made 80% or more of the commits and is gone by this page's definition.
- Parallel Dev — people editing the same files in the same week.
- Commit Timing — when the team commits, behind the off-hours row on a person's card.
- AI & Co-authors — how much AI helped, and who is credited together.