
Busfactor
io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026
Map single-author, never-reviewed files from authorship and review data: a factual risk list.
Overview
Busfactor's local MCP server; no sign-in required; STDIO.
No AI overview yet: these facts come from the registry entry and the server itself.
Installation
In SourceWeft
- Open Busfactor in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
busfactor
Every codebase has files that only one person really knows. If that person is away — on holiday, off sick, gone from the team — those files are the ones nobody can safely change. busfactor works out where that risk sits. You give it, for each file, who wrote it and how many commits each author made, plus who reviewed changes to it, and it gives back a factual map:
- Per-file entries — for every file, its
total_commits, how many distinct authors it has, itstop_authorand that author'stop_shareof the file's commits, andexternal_reviewers: how many of its reviewers are not authors of the file. A review by one of the file's own authors does not count as external review, so a file checked only by the people who wrote it reads as never reviewed. - Two flags, one list — a file is
dominatedwhen its top author's share reaches the threshold (0.8 by default), andnever_reviewedwhen it has no external reviewers. A file that is both isat_risk, andat_risk_filescollects exactly those paths. The list is a statement of fact about concentration and coverage; it carries no judgement about the people involved. - Summary counts — how many files were analysed, how many are at risk, how many have a single author, and how many were never externally reviewed.
Duplicate author names inside one file are merged by
summing their commits before anything is computed, and
reviewer names are de-duplicated. The top-author share is
rounded to four decimal places, and the domination check
compares that rounded share — the number the report itself
shows — against the threshold, so a file reported at
exactly the threshold is always flagged dominated. Every
list in the result is sorted ascending, so the same data
always yields exactly the same map. Malformed input — a
missing or empty file list, a duplicate path, an author
with no commits — is a validation error naming the
offending path (for example
files[1].authors[0].commits must be an integer >= 1),
and no partial map is produced. The computation is pure
and local: no network, no configuration, no files read
beyond the input you pass in.
CLI
args.json contains the full arguments object:
reviewers defaults to [] per file, and threshold
defaults to 0.8. Here src/solo.ts is single-author and
unreviewed, while src/shared.ts is split evenly and was
externally reviewed by cleo. The map is printed as JSON:
Exit codes: 0 on success, 1 on a runtime error (including
an unreadable or invalid input file, or invalid input), 2
on a usage error.
MCP server
MCP client config:
Tools
-
analyze_bus_factor— Map single-author, never-reviewed files from authorship and review data.files(array, required, at least one) — files as{path, authors, reviewers?}objects;pathis unique across the set, eachauthorsentry is a{name, commits}pair with at least 1 commit, andreviewerslists names that reviewed changes to the filethreshold(number, optional, default 0.8) — the top-author share at or above which a file counts as dominated by one author; must be > 0 and <= 1
Returns
{files, at_risk_files, summary}.
Docker
Development
License
MIT — Copyright (c) 2026 Rene Turcios
Source: README.md at commit 154faf7
Tools
0Version history
1- v0.1.0LatestNov 3, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts