Appearance
Handoffs
This lens answers: who took each package over from whom, and which packages did nobody pick up when their owner went quiet? Ownership shows who leads each package in the analyzed period. Handoffs shows how it got that way.
An "owner" here is a rule about commits, not a fact about your team. The person who made the most commits in a package for long enough counts as its owner, whether or not anyone gave them the job. Someone who runs a package through reviews and design, without committing much, won't show.
Unlike most lenses, this one reads all of the repository's history, whatever --since says. See What "all of history" means.
Reading the numbers
| What you see | What it means |
|---|---|
| "2 packages whose owners went quiet while work went on, and nobody took them over" | The large number on the card: the packages that are unclaimed. With none, the large number is the handoffs instead, as in "5 handoffs, and no package is unclaimed." |
| "5 handoffs across 3 packages, over all of history." | Every handoff GitRelic found and every package it rated. The root and dot-folders aren't in either number. |
| "services/checkout is unclaimed: its owner went quiet, work goes on (23 commits since), and nobody has taken it over." | The owner has no commit anywhere in the repository for over 90 days, and this package has had 10 or more commits since their last. The commit count only appears when one package is unclaimed. With several, the table has each count. |
| "Noor Haddad took over 3 packages, more than anyone." | The count is of takeovers, so someone who took the same package twice counts it twice. It appears from 2 takeovers up. When people tie, it names the one whose takeovers came earlier on average, even though "more than anyone" isn't strictly true then. |
| "...and has gone quiet: 2 of theirs are unclaimed." | "Of theirs" means the packages they own now, including any they were the first owner of. This number can be larger than the takeovers. |
| "5 handoffs since 2021 Q1; the most in 2024 (3)." | "Since" is the first quarter any rated package changed, not the first handoff. This line appears from 5 handoffs up. When years tie, it names the latest. |
| "sdk went quiet with its owner: little has changed since." | The owner is quiet and the package has had fewer than 10 commits since. Chips in the findings drop a leading packages/ from the name. |
| "Mei Lin has owned every package from the start: nothing has changed hands." | Mei is the only owner the rules found, and there are no handoffs. Other people may well commit there. It also appears when other packages never had an owner at all, so "every package" can overstate it: check the table. |
| "The root and dot-folders (1) are left out." | Files at the top of the repository, or in folders like .storybook, form packages of their own. They were rated and aren't shown. The number is how many. |
| "The history before this window couldn't be read, so these handoffs cover the window only." | Reading the older history failed. Treat the numbers as partial. See What "all of history" means. |
| "This report was made before the Handoffs lens: rerun gitrelic to see how ownership moved." | The lens has no data. Rerunning usually fixes it. |
Each package's state
| State | What it means | Commits since owner left |
|---|---|---|
| Unclaimed | The owner is quiet, the package has had 10 or more commits since their last commit, and nobody has taken over. This one's worth acting on. | 10 or more |
| Went quiet | The owner is quiet, and the package has had fewer than 10 commits since. It may be finished or forgotten. | 0 to 9 |
| Held | The owner has committed in the last 90 days, anywhere in the repository. | Empty |
| Never one owner | No quarter ever had a leader, so the package has always been shared. | Empty |
Held doesn't mean the owner is working on the package. Someone who stopped touching a package years ago and now works elsewhere in the repository still holds it, until someone else takes over.
Unclaimed doesn't mean nobody is stepping up. A newcomer who has led one quarter hasn't taken over yet, so the package reads as unclaimed until they lead a second.
Four example repositories
These repositories are invented, but each result is what GitRelic reports for commits like these.
A Go backend where work changed hands in the open
Noor Haddad took over 3 packages, more than anyone.
5 handoffs since 2021 Q1; the most in 2024 (3).
The card's large number is 5, "handoffs, and no package is unclaimed." Hovering Noor shows:
Noor Haddad
Took over 3 · handed on 2
Owns 1 today
What it means: ownership moves here and someone always picks it up. Every package is held. Noor took over three packages in 2024 and has since passed two on, so the person who took the most isn't the person holding the most. The cluster in 2024 is worth asking about, and may be a reorganization.
What to look at: the table shows who owns each package now and since when. Select services/auth to see its three owners in order.
A Python platform whose main owner left
services/ingest and services/models are unclaimed: their owners went quiet, work goes on, and nobody has taken them over.
Greta Lund took over 2 packages, more than anyone, and has gone quiet: 2 of theirs are unclaimed.
sdk went quiet with its owner: little has changed since.
The root and dot-folders (1) are left out.
The table says 36 commits since the owner left for services/ingest, and 18 for services/models. Hovering the curve for services/ingest adds "Unclaimed: 36 commits since Lund went quiet."
What it means: Greta inherited both packages from Olaf Dahl, then stopped committing. Three people have kept changing them, in about equal shares, so no one reaches 40% of a quarter's commits and nobody counts as the new owner. The work is real and nobody clearly leads it.
sdk is a different question. Its owner left too, but only 3 commits have landed since. It may be finished, or it may be forgotten and still in use.
What to look at: Experts shows who to ask about the two unclaimed packages today, which is a good start on naming a successor. For sdk, check whether anything still depends on it.
A Java repo with one unclaimed package and no handoffs
services/checkout is unclaimed: its owner went quiet, work goes on (23 commits since), and nobody has taken it over.
The picture has no curves, only this line:
No package has changed hands: each is still with its first owner.
The table has three packages:
| Package | Commits | Owner | Since | Handoffs | State | Commits since owner left |
|---|---|---|---|---|---|---|
services/checkout | 53 | Lev Oren | 2023-01 | 0 | unclaimed | 23 |
services/orders | 36 | 0 | never one owner | |||
services/search | 24 | Pia Holm | 2024-04 | 0 | held |
What it means: the picture draws handoffs, so a package that's unclaimed without ever changing hands has nothing to draw. Only the findings and the table show it, which is why they matter. services/orders has never had an owner, so "each is still with its first owner" doesn't cover it. Three people share it evenly, which may be just fine.
The most recent quarter in this repository has Kai Dunn leading services/checkout for the first time. That isn't a handoff yet. If Kai leads the next quarter too, the package becomes held, the unclaimed line goes away, and a handoff from Lev to Kai appears, dated to Kai's first leading quarter.
A Rust tool with one author
Mei Lin has owned every package from the start: nothing has changed hands.
The picture says:
Mei Lin has owned every package since Jan 2024: nothing has changed hands.
What it means: one person, no history of moving hands. That's normal for a young or one-person repository, and it's a real answer. The risk this creates is one person's whole project, which Ownership covers. If you know there have been other maintainers, check whether their commits were squashed under one name.
How it's measured
What "all of history" means
A default run analyzes the last 12 months, and most lenses count only those commits. This lens also reads the commits before that period, back to the repository's first commit on the analyzed branch. A 12-month window would otherwise hold only the handoffs from those 12 months, and every long-standing owner would look like the package's first.
What this means when you read it:
--sincealmost never changes the answer. Runs with--since alland with a recent date normally give the same handoffs, owners, states and commit counts. The window only has to contain at least one commit, or GitRelic stops and says so. There are two exceptions. A commit made at exactly the start of the period is counted twice, so a count can be one too high. And when a commit's date is older than the period's start but commits made before it are newer, such as after a rewrite that backdated a commit, git can stop reading at that commit on a run with a period, so the commits behind it can be missed, here and on every other lens. It's rare and usually a few commits, and--since allreads them all.- Some numbers beside this lens do follow
--since. On a person's card, Took over is all of history, and Commits is the analyzed period. So a card can say "Took over 3 packages" over a small commit count. On a package's card, File changes is the analyzed period too, as is the time strip. The Commits column in this lens's table counts all of history, so it's often larger than the same package elsewhere. - People who left before the period still appear. They're named here, can be selected and searched for, and their card says "none in this window" for commits.
- Only the author, date and file list are read from the older history, which is all this lens needs. Co-author trailers aren't counted in any period.
- Identities are merged across the whole history, so someone whose old email only appears before the period doesn't hand a package to themselves.
If the older read fails, for example by hitting the time limit on a very large repository, the lens runs on the analyzed period alone. The findings lead with a warning, the card says "over this window only," and a line goes to stderr: [gitrelic] file ages cover the analysis window only:, with the reason. In that report:
- Earlier handoffs are missing, and the first leader inside the period looks like the package's first owner.
- A package needs its 20 commits inside the period.
- Identities aren't merged with the older history, so an old email can look like a different person.
Give git longer with --git-timeout <seconds>.
A shallow clone gives no warning. GitRelic can only read what's in the clone, so a clone made with --depth reports fewer handoffs, later owners, and "over all of history" as usual. Fetch the full history first.
From commits to owners
GitRelic counts commits per package, per calendar quarter (in UTC, by each commit's author date), then applies these rules:
| Term | Rule |
|---|---|
| A quarter's leader | The person who made the most of the package's commits that quarter, if they made 40% or more of them and the quarter had 4 or more. Other quarters have no leader. Ties go to the alphabetically first email. |
| Owner | The first leader owns the package until someone takes over. |
| Handoff | A newcomer leads two quarters with nobody else leading between them. Quarters with no leader don't interrupt them. The handoff is dated to their first leading quarter. |
| Quiet | No commit anywhere in the repository for more than 90 days before the newest commit. |
Here's one package, quarter by quarter:
| Quarter | Commits | Leader | What happens |
|---|---|---|---|
| 2023 Q1 | Ana 6 | Ana | The first leader, so Ana owns the package |
| 2023 Q2 | Ana 3 | Nobody | Fewer than 4 commits |
| 2023 Q3 | Noor 5, Ana 3 | Noor | Noor's first leading quarter |
| 2023 Q4 | Noor 2, Ana 2, Ivy 2 | Nobody | Nobody reaches 40%, and Noor's run continues |
| 2024 Q1 | Noor 4, Ana 2 | Noor | Noor's second: a handoff from Ana to Noor, dated 2023 Q3 |
| 2024 Q2 | Noor 4 | Noor | Noor's time as owner extends |
GitRelic reports one handoff. The table says Noor has owned it since 2023-07, the first month of that quarter. Had Ana led 2023 Q4 instead, Noor's run would have ended and the handoff wouldn't have happened in 2024 Q1.
Why two quarters. One strong quarter can be a project, a release or someone covering a vacation. Asking for two keeps those out, so a takeover that reverses in the next quarter isn't a handoff.
Three consequences are easy to miss:
- Handoffs show up late and dated early. A handoff doesn't exist until the second leading quarter, then appears back at the first one. A new report can add a handoff to a past quarter.
- A run can span a long time. Quarters with no leader don't break it, so a newcomer who led in 2019 and leads again in 2026, with nobody leading between, takes over dated 2019. Their time as owner is drawn from 2019 too. If a date looks odd, select the package and check.
- Two rival newcomers can block each other. If they take turns leading, neither gets two in a row, so the package stays with its old owner, and reads as unclaimed if that owner has gone quiet.
From owners to states
Once the owner is known, only one thing decides the state: when that owner last committed anywhere in the repository.
"The last 90 days" is counted back from the newest commit, not from today, so a report on an old commit says what was true then. A person exactly 90 days back isn't quiet yet. A commit to any file counts as being active, even a config file, and the newest commit sets the date even if it's a bot's. A repository where only Dependabot has committed for four months has every person quiet.
"Commits since" counts from the owner's last commit anywhere in the repository, not their last in the package. It counts everyone's commits to the package after that date.
What counts
- A package is rated from 20 commits over its history. A commit counts once per package, however many of its files it changed.
- Packages are the repository's own declared workspaces, else
packages/*,apps/*,libs/*orservices/*, else the top-level folder, as on Ownership. The workspace list is read at the analyzed commit and applied to all of history. - Fixtures and generated files don't count, unless you pass
--include-fixtures. Project plumbing (manifests, lockfiles, changelogs, licenses, CI and tool configuration) never counts. Test files do. A commit touching only files that don't count still shows its author as active. - Merge commits don't count, and neither do bots.
- AI agents count like people. An AI agent committing under its own account can lead a quarter, take over a package and appear in the picture, as
claude[bot]would. Commits by a person with an AI trailer count as that person's. - Only the commit's author counts, never its co-authors.
- One person, many emails. Identities are merged as on Contributors. When GitRelic can't tell, you may see a handoff from someone to themselves. Add the two addresses to
.mailmap, or keep the mapping out of the repository withgit config mailmap.file ~/my-mailmap. With--no-merge-identities, someone who changed email reads as "Ana Ruiz → Ana Ruiz."
In the dashboard
Find this lens under Ownership & Knowledge. Its badge counts unclaimed packages and appears from one. Elsewhere, the Overview shows the same reading, such as "2 unclaimed" or "5 handoffs."
- The picture has time along the top, from the first change in any rated package to the last. Each dot is a quarter with a handoff, and more handoffs make a bigger dot. Along the bottom is everyone who took a package over, ordered by when. Each curve is one handoff, falling from its quarter to the person who took over, and in their color, so one person's takeovers gather into one strand. An unclaimed package with no handoff draws nothing here.
- People are drawn as a filled dot when active and a ring when quiet. More takeovers make a bigger mark. They're labeled with the last word of their name, then "took 3," and "2 unclaimed" if any of the packages they own now are. People who owned a package but never took one over don't appear along the bottom.
- Colors go to the six people with the most takeovers, listed with their counts on the card. Everyone else is grey, including an owner who never took anything over.
- Hover a curve for its package, quarter and who handed it to whom. Hover a dot for that quarter's handoffs, up to 8. Hover a person for "Took over 3 · handed on 2" and "Owns 1 today."
- Select a person by clicking them, or a name on the color key or in the findings, to light what they took over and what they handed on.
- Select a package by clicking a curve, a chip, a table row or searching for it. Its handoffs light up, and its reigns appear under the time axis: a bar for each owner, in their color, with its name and state beneath ("2 owners · unclaimed, 36 commits since its owner went quiet"). A bar runs from the owner's first quarter to the last quarter they led, so there can be gaps between owners. A tail shows work going on after the last bar: bright for unclaimed, grey for went quiet. Hover a bar for its dates.
- The time strip under the picture shows only the analyzed period, like the rest of the dashboard. With a selection, it shows the selection's commits in that period.
- The inspector, with nothing selected, shows the numbers and findings quoted above, the color key and a link to the table. A person's card adds a Took over row when they took or handed on anything. A package's card shows its size and activity, and Who to ask when Experts rates it.
- The table (
T) lists every rated package, most commits first: commits, owner, since when, handoffs, state, and commits since the owner left. Since is the first month of the quarter the current owner's time began. The tiers are the four states, and they describe where a package stands.
Sometimes there's nothing to draw, and the picture says why:
| The picture says | When |
|---|---|
| "No package has 20 or more commits in its history." | No package is rated. A repository with all its files at the top level also gets this, however many commits it has, since the root is left out. |
| "Mei Lin has owned every package since Jan 2024: nothing has changed hands." | No handoffs, and only one person is an owner. |
| "No package has changed hands: each is still with its first owner." | No handoffs, and more than one owner. It can also appear when no package ever had an owner, which the table will show. |
With no handoffs at all, selecting a package draws no reigns. Use the table.
A package with no files left at the analyzed commit, because it was deleted or renamed, stays in the table and the findings but can't be selected, so it has no reigns.
What it can't tell you
- Who actually owns a package. The owner made the most commits. A reviewer, architect or manager who steers a package without committing much doesn't count, and whoever holds the keyboard does.
- Whether a quiet owner has really left. Quiet means no commits for 90 days. They may be on leave, in another repository, or reviewing every change.
- Whether a held package is being looked after. Held only says that its owner committed somewhere in the repository lately.
- What moved. Renaming a folder starts a new package: the old name keeps its commits and stays in the table, with a state that depends on its old owner, and the new name starts from the move with no handoff. The commit that moves files counts for the new name, and a commit that deletes files counts for the package they were in.
- Whether a deleted package matters. Packages are found from the history, so one that no longer exists can still be rated, with a state. Check that it's still there before acting on it.
- Who wrote squashed work. A squash merge credits one author with what may be several people's commits, which can make one person look like a package's leader, or hide a handoff.
- Work on branches that aren't merged. Only the analyzed branch's history counts.
- Changes inside a quarter. Quarters are coarse, and a takeover that lasts one quarter isn't a handoff, by design. The rules are the same for a 30-commit package and a 3,000-commit one.
Related
- Ownership — who leads each package in the analyzed period. It uses different rules (10 commits, 30% of them, with no two-quarter rule), so its top contributor can differ from the owner here.
- Experts — who to ask about a package today, which is where to start with an unclaimed one.
- Contributors — who is active, quiet or gone. Its "quiet" follows the length of the analyzed period, so it can differ from the 90 days here.
- Age — how long files and packages have gone unchanged, for a package that went quiet.
- Renames — what a move does to a package's commits, when a package seems to appear from nowhere.
- AI & Co-authors — how AI agents and bots are recognized.