Skip to content

Ownership ​

This lens answers: who owns what, how much of it rests on one person, and how many people does the code depend on? Its headline is the bus factor: how many people would have to leave before more than half the files have nobody left who wrote them.

Everything here is read from commits, so it measures who changed the code, not who understands it. Someone who reviews a package closely but rarely commits to it doesn't appear, and it only sees the analyzed period, which is the last 12 months by default (the dashboard calls this "this window").

Reading the numbers ​

What you seeWhat it means
"3 people would have to leave before half the files have nobody left who wrote them"The repository's bus factor. It's about files, not packages, and it ignores whether those people are still around: see the method.
"Lena Voss, Omar Reyes and Dev Anand"The people that count removes, in the order it removes them: whoever is an author of the most files goes first. It isn't a ranking by commits, so a package's top contributor may not be named.
"The bus factor, over the 32 files with two or more commits in this window."How many files it was worked out from. Files changed once aren't counted. With no such file, the headline doesn't appear.
"0 people would have to leave…"More than half the counted files have no author to begin with. That takes about 50 or more changes to a file with nobody standing out, so it's rare, and it doesn't mean the code is safe.
An email address in that listThat person has no share in any package the lens lists, so the card has no name for them.
"services/billing's top contributor, Marta Quill (87%), has made no commit in 90 days: find out who takes it over."The person with the most commits in the package is quiet, and the share is their part of its commits. This is the finding to act on, and the lens's badge. The name is shortened, so packages/auth reads "auth".
"services/billing and auth rest on one person (75% or more of the commits)."Their top contributor made at least 75% of the commits. That's normal for a young package or a small tool, and a risk for code many people depend on. It doesn't say whether that person is still active.
"1 package of 4 is shared: nobody made 30% of the commits."These packages have no owner. That's often healthy, though nobody may feel responsible for them either.
"Rin Halloran tops every package: one person owns everything, so the map has one color."The same person has the most commits in every package on the map. It's true of a solo project. It's overstated elsewhere: it only checks who is first, so it also prints for a team whose only package is led by one person with 28%. Beside "1 package of 1 is shared," trust the second line.
"1 package with under 10 commits and the root and dot-folders (1) left off the map."Packages too small to rate, and the root and top-level dot-folders such as .github, which aren't drawn or listed. Their files still count toward the repository's bus factor.
"The map shows the busiest 60 of 72 packages; the other 12 are in the table."The map stops at 60. The findings and the table cover them all.
People who know it (table)People with at least 10% of the package's commits and at least 3 commits. It can be 0 when many people each made a commit or two.
Bus factor (table)The same count as the headline, using only that package's files. 0 usually means none of its files has two or more commits, so there was nothing to count. A package can have eight people who know it and a bus factor of 1, because the two numbers measure different things: see the method.
Tops packages (person card)How many packages this person has the most commits in, with no minimum share.
If they left: "every package has someone else" or "1 package with nobody else"Packages where this person is the only one who knows it. "Someone else" only means they meet that bar: they may be long gone themselves, so check the package's tooltip. A package nobody knows isn't counted.
"(quiet)" after a nameNo commit in the 90 days before the newest commit. See what quiet means, since the same person's card can say Active.
Bus Factor: "2 (Gil Sato: 85%)" (file card)Not a bus factor, despite the label. On a file, the first number is how many people have changed it, and the name is whoever made the most of its commits. It's highlighted when the file's risk is critical.
Owner Inactive: "Gil Sato (237 days)" (file card)This is a ghost file.
"1 owner quiet" or "bus factor 3" (Overview)The lens's reading: quiet top contributors if there are any, else the bus factor. "—" means no package could be rated.

The table's tiers are Shared (nobody at 30%), Owned (30% or more), One person (75% or more) and Top quiet. A package sits in the last that applies, so one that's both one-person and quiet is under Top quiet, and the flags column names both.

What each number is computed on ​

These numbers come from different places, so they don't have to agree:

NumberComputed forWhat it countsMinimum
Bus factor (headline)The repositoryThe authors of each fileFiles need 2+ commits
Bus factor (table)One packageThe authors of each file in itPackage needs 10+ commits for a row, files need 2+
Top contributor, share, owner, one person, knows itOne packageCommits to the packagePackage needs 10+ commits
"Quiet"One personTheir last commitNone
Bus Factor row (file card)One filePeople and commits on that fileNone
File riskOne filePeople and commits on that file8+ commits, or no risk is given
Ghost fileOne fileTop author's share, and whether they're goneNone

What "quiet" means ​

Here, quiet is a flat rule: no commit in the 90 days before the newest commit analyzed. It doesn't change with the period, and Experts and Handoffs use the same rule.

Contributors uses the word differently. There, quiet is the middle of three statuses, between active and gone, and those cutoffs stretch with the period. The status on a person's card comes from Contributors, so the two can disagree on one screen. For someone with no commit for this long:

No commit forHereContributors, default 12 monthsContributors, 18 monthsContributors, six years
99 daysquietquietactiveactive
199 daysquietgonequietactive
399 daysquietnot in the periodgoneactive
1,199 daysquietnot in the periodnot in the periodgone

"Newest commit" includes a bot's, so a release bot still running keeps the clock moving while the people have stopped. On a period of 90 days or less nobody can be quiet: nobody has been absent long enough for it to show.

Four example repositories ​

These repositories are invented, but each result is what GitRelic reports for commits like these.

A Rust tool with one maintainer ​

1 person would have to leave before half the files have nobody left who wrote them

Rin Halloran

The bus factor, over the 18 files with two or more commits in this window.

Rin Halloran tops every package: one person owns everything, so the map has one color.

Hovering the one package says "386 commits · 3 people", then "Rin Halloran: 98%", "Sam Ode: 1%", "Teo Brand: 1%" and "Rests on one person". Selecting Rin in the Mosaic adds: "If Rin Halloran left, 1 package would have nobody left who knows it."

What it means: this is correct, and not a problem to fix by itself. It's a one-person project, and the lens says so plainly rather than leaving a one-color map to imply something. Sam and Teo made a handful of fixes and don't reach the 3-commit, 10% bar to "know" the package.

A TypeScript monorepo where an owner went quiet ​

3 people would have to leave before half the files have nobody left who wrote them

Lena Voss, Omar Reyes and Dev Anand

The bus factor, over the 32 files with two or more commits in this window.

services/billing's top contributor, Marta Quill (87%), has made no commit in 90 days: find out who takes it over.

services/billing and auth rest on one person (75% or more of the commits).

1 package of 4 is shared: nobody made 30% of the commits.

1 package with under 10 commits and the root and dot-folders (1) left off the map.

PackageCommitsTop contributorShare %People who know itBus factorFlags
apps/storefront390Lena Voss6222
services/billing172Marta Quill8721top quiet, one person
packages/auth148Omar Reyes8121one person
packages/search92Lena Voss2843shared

What it means: a repository bus factor of 3 looks fine, and it doesn't name Marta, because it goes by files and services/billing holds only 8 of the 32. That package is the real risk: Marta made 87% of its commits and stopped 124 days ago. Marta's card says "every package has someone else": that someone is Dev Anand, whose 22 commits there clear the bar, so ask Dev first. But Dev has only 13% of it, and the package's own bus factor is 1, so that's a thin handover.

Also in this repository: Gil Sato's last commit was 237 days ago, past Contributors' cutoff for gone. Gil tops no package, so the map says nothing about them, but two files in packages/auth are ghost files. The file card for session.ts, which Gil made 11 of 13 commits to, shows:

Bus Factor: 2 (Gil Sato: 85%)

Owner Inactive: Gil Sato (237 days)

Find it a new owner. Gil Sato wrote 85% and hasn't committed in 237 days.

saml.ts gets the same advice at 100%, from a single commit, so check a file's commit count before acting. And Marta's files aren't ghost files yet: at 124 days, Marta is quiet, not gone. The two signals catch different people.

A Java team that shares everything ​

3 people would have to leave before half the files have nobody left who wrote them

Dee Lund, Cy Park and Ana Ruiz

The bus factor, over the 55 files with two or more commits in this window.

3 packages of 3 are shared: nobody made 30% of the commits.

PackageCommitsTop contributorShare %People who know itBus factorFlags
services/orders327Ben Holt2364shared
services/ledger265Ana Ruiz2653shared
libs/common150Dee Lund2362shared

What it means: this is a shape many teams want, and the Mosaic agrees: "If Ben Holt left, every package they work on still has someone who knows it." It also shows why bus factor is never close to headcount. Six people work on everything, but the count is 3, because a file's authors are usually only a few of the people who changed it. And Ben tops the biggest package without being named, since the list goes by files authored rather than commits.

What to look at: nothing is on fire. The faint map is the question to ask: with no owner anywhere, does someone feel responsible for libs/common?

A Python repo read over two windows ​

With the default 12 months:

1 person would have to leave before half the files have nobody left who wrote them

Tess Amaro

The bus factor, over the 23 files with two or more commits in this window.

ranking's top contributor, Noor Haddad (55%), has made no commit in 90 days: find out who takes it over.

ingest rests on one person (75% or more of the commits).

2 packages with under 10 commits left off the map.

The same repository with --since all, six years of history:

2 people would have to leave before half the files have nobody left who wrote them

Tess Amaro and Noor Haddad

The bus factor, over the 30 files with two or more commits in this window.

ranking's top contributor, Noor Haddad (92%), has made no commit in 90 days: find out who takes it over.

export's top contributor, Ivo Stark (92%), has made no commit in 90 days: find out who takes it over.

ingest, ranking and export rest on one person (75% or more of the commits).

1 package with under 10 commits left off the map.

What it means: neither is wrong. Twelve months asks who's doing the work now: Tess, and it's why Ivo's export falls below the floor. Six years asks who built this, and shows Noor and Ivo behind two whole packages. The higher bus factor isn't good news, since it counts Noor, who has already stopped committing. A bus factor never checks whether its people are still here.

Watch the statuses: on both runs Noor reads "(quiet)" on the map, 199 days after their last commit. Their card reads Gone on the default run and Active on the long one. Ghost files move too: the default run has four, including scripts/backfill.py, and the six-year run has none, because gone now starts past 1,000 days.

What to look at: use the default for who's holding things now, and --since all for what would be lost. If the answer to "who takes over ranking?" is unclear on both, try Experts.

How it's measured ​

GitRelic reads the commits in the analyzed period and leaves out merge commits.

Who counts. People and AI agents. Bots never count: see what counts as a bot. Only the commit's author counts: being named in a Co-authored-by: trailer adds nothing. Identities are merged first.

Which files count. Generated files, fixtures and snapshots are left out, unless you pass --include-fixtures. Project plumbing (manifests, lockfiles, changelogs, licenses, CI and tool configuration) is always left out, and the flag doesn't bring it back. Tests count.

Packages come from the repository's own workspace files, else packages/*, apps/*, libs/* and services/*, else the top-level folder. A file directly in the root belongs to the root.

Who owns a package ​

A commit counts once in each package it touched, however many of its files it changed. Files since deleted or renamed count too, because that work happened there, so a person can top a package for work that no longer exists.

TermRule
Rated10 or more commits in the package.
Top contributorThe person with the most commits in the package.
OwnerThe top contributor, when they have 30% or more. Below that the package is shared.
Rests on one personThe top contributor has 75% or more.
Knows it10% or more of the package's commits, and at least 3 of them.
QuietNo commit in the 90 days before the newest commit analyzed.

The bus factor ​

This is the truck factor method from Avelino et al., A novel approach for estimating truck factors (ICPC 2016). It reads only files that still exist and have two or more commits.

A file's authors come from three things: who changed it first in the period, how many changes each person made, and how many changes everyone else made. Being first is worth about seven changes. Someone is an author when their score is high enough by itself, and at least 75% of the top score on that file.

It helps to see what that does with one file's changes, oldest first:

ChangesAuthors
Ana, BenAna
Ana, Ana, BenAna
Ana, Ben, BenAna and Ben
Ben × 5, Ana, BenBen
Ana, then Ben × 11Ana and Ben
Ana, then Ben × 12Ben
Eight people, two changes eachWhoever was first

So one change late on doesn't make someone an author, but being first can. "First" means first in the analyzed period, which on a 12-month run is rarely who wrote the file. That last row is why evenly shared code can have a low bus factor: when eight people share a package this evenly and the same person is first on every file, the count is 1, while the table says all eight know it.

The repository's count uses every file that qualifies, including those in the root, in dot-folders and in packages too small to rate. A package's count uses only its own files. Neither looks at whether anyone has gone quiet.

File risk ​

Each file also gets a risk, read by other lenses. It's based on that file's people and commits, not the method above, and it needs 8 or more commits: under that, the file has no risk, though its authors still show. That's the floor every per-file verdict shares: see Fix rate.

RiskRule
CriticalOne person only, or the top person has 90% or more
HighThe top person has 75% or more
MediumThe top person has 50% or more
LowEverything else

The words themselves aren't printed on this lens. A critical file has its Bus Factor row highlighted on the file card, and if it's also a hot file whose author isn't gone, the card suggests "Pair on it, or split it, before only one person can change it."

Ghost files ​

A ghost file is one whose main author has stopped committing: one person made 80% or more of its commits, and that person is gone. Others may still be changing it, so it can look healthy while the person who knows it best has moved on.

"Gone" is the Contributors status, not the 90-day quiet rule. A person is gone when their last commit is further back from the newest commit than 180 days or half the analyzed period, whichever is longer. "Half the period" means half the time from the first commit to the last one in it.

That means the cutoff depends on --since, and a longer period doesn't simply find more:

PeriodGone starts atWhat it can find
6 months or less180 daysNext to nothing. Almost nobody in the period can have been away that long.
12 months (default)About 180 daysPeople who stopped 6 to 12 months ago
18 monthsAbout 270 daysPeople who stopped 9 to 18 months ago
Six yearsAbout 1,100 daysPeople who stopped 3 to 6 years ago, and nobody more recent

Someone who stopped before the period began has no commits in it, so they can't be a file's main author. Widen --since to reach them.

There's no list or count of ghost files in the dashboard, and they don't draw on the map. They appear when you select a file in any lens: its card gains the Owner Inactive row and, first under what to do, "Find it a new owner." The whole list is in the --json output.

The days count back from the newest commit analyzed, not from today.

There's no minimum number of commits. A file changed once by someone now gone is a ghost file at 100%, with the same warning as one they changed fifty times. Unlike file risk, the 8-commit floor doesn't apply, so read the commit count on the same card.

How it differs from the map's dashed outline:

Dashed outlineGhost file
Applies toA packageA file
Person's shareMost commits, any share80% or more
Person's absence90 days, alwaysGone: 180 days or more, growing with the period

How it differs from cold files. A ghost file has at least one commit in the analyzed period. A file with none is never a ghost file, whoever wrote it. Age dates those, and flags the old ones nobody left has changed.

In the dashboard ​

Find this lens under Ownership & Knowledge.

  • The map is the main picture. Each cell is a package, sized by its commits and colored by its top contributor. The bright core inside each cell is that person's share: about a third of the cell at 25% or less, and all of it at 75% or more. The six people who top the most packages get a color and everyone else is grey. A dashed outline means the top contributor is quiet. Select a person to dim the packages they don't top. Up to 60 packages are drawn.
  • The Mosaic (the corner toggle) shows every share, not just the top one. Each column is a package, as wide as its commits, split from the bottom by each person's share, with people past the six colors stacked as one grey block on top.
  • What if someone left? In the Mosaic, select a person. Their share fades, and a strip in the accent color marks each package where they're the only one who knows it ("Nobody else knows it: Tess Amaro is its only knower."). A line above the chart counts them: "If Tess Amaro left, 1 package would have nobody left who knows it."
  • Hover a package for its path, commits and people, its top four contributors with their shares, and its flags: "Rests on one person", "Shared: nobody above 30%" and "Top contributor quiet 90+ days".
  • The inspector, with nothing selected, leads with the bus factor and the people behind it, then the findings quoted above, then the color key with a "(quiet)" beside anyone quiet. A person's card adds Tops packages and If they left. A package's card gives its size, its activity and, when Experts rates it, who to ask.
  • The table (T) lists every rated package except the root and dot-folders: commits, top contributor, share, people who know it, its bus factor and flags. It's the only place a package's own bus factor appears.
  • The badge appears at one package with a quiet top contributor. Its tooltip says "1 package whose top contributor went quiet".
  • The portfolio page, when several repositories are served, shows each one's bus factor.

If no package has 10 commits, the map says "No package has 10 or more commits in this window." If the period's commits were only bots' or only touched project plumbing, the inspector says "This report was made before the Ownership lens: rerun gitrelic to see who owns what." Rerunning won't help there: there's just no ownership to read.

What it can't tell you ​

  • Who understands the code. Commits aren't knowledge. A reviewer or a former author who still answers questions doesn't show, and someone who changed a file on request does.
  • Why someone stopped. Quiet and gone mean no commits, not that a person left. Leave, a new team and a move to reviewing all look the same.
  • Who has already left, in the bus factor. The count treats a person gone for months like anyone else, so it can be higher than the people actually here. Read it beside the dashed outlines.
  • How big a commit was. A one-line fix and a whole feature each count once, and a repo-wide reformat counts in every package it touched.
  • What happened before the period. Someone who wrote a package years ago and stopped doesn't appear at all on the default run.
  • What happened before a rename. A file's history starts at its new name for these counts, and whoever moved it becomes its first author, so a person who only moved a file can be its author, and a file moved after its owner left isn't a ghost file. Renames covers moved files.
  • Who's one person. Two emails with different names count as two people until they're merged.
  • Work shared by a few. A file three people split evenly never reaches the 80% for a ghost file, even if all three have gone.
  • Experts — who to ask about a package, weighing recent work more, over all of history.
  • Handoffs — who took each package over from whom, and what nobody picked up.
  • Contributors — active, quiet and gone, and files owned, the count on a person's card.
  • Coupling — which packages change together. A coupled pair with different owners means a change often needs two people.
  • Age — files nobody has changed in a year, and the ones nobody left has changed.
  • Cursed Files — reads file risk: a critical file is a candidate and scores 30 points, a high-risk file 15, and any other with more than five people 10. Whether the owner is gone adds nothing to the score: ghost files aren't part of it.
  • AI & Co-authors — who is credited together. A person working with AI looks like one person here.

Released under the MIT License.