Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Map single-author, never-reviewed files from authorship and review data: a factual risk list.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"busfactor": {
"command": "npx",
"args": [
"-y",
"@reneturcios/busfactor",
"mcp"
]
}
}
}在终端中运行这条命令
claude mcp add busfactor -- npx -y @reneturcios/busfactor mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"busfactor": {
"command": "npx",
"args": [
"-y",
"@reneturcios/busfactor",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"busfactor": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/busfactor",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 CloudCorpRecords 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.0)于4天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js, Docker。
同一分类中有:Spec Driven Development, Remote Desktop Commander, dotnet-mcp
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
MCP server for .NET symbols, XAML, source generators, and restricted workspace edit
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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:
total_commits, how many distinct authors it has, its top_author and that author's top_share of the file's commits, and external_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.dominated when its top author's share reaches the threshold (0.8 by default), and never_reviewed when it has no external reviewers. A file that is both is at_risk, and at_risk_files collects exactly those paths. The list is a statement of fact about concentration and coverage; it carries no judgement about the people involved.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.
npx @reneturcios/busfactor analyze --input args.json
npx @reneturcios/busfactor --version
args.json contains the full arguments object:
{
"files": [ { "path": "src/solo.ts", "authors": [{ "name": "amy", "commits": 10 }] }, { "path": "src/shared.ts", "authors": [ { "name": "amy", "commits": 5 }, { "name": "bob", "commits": 5 } ], "reviewers": ["amy", "cleo"] } ] }
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:
{
"files": [ { "path": "src/shared.ts", "total_commits": 10, "distinct_authors": 2, "top_author": "amy", "top_share": 0.5, "external_reviewers": 1, "never_reviewed": false, "dominated": false, "at_risk": false }, { "path": "src/solo.ts", "total_commits": 10, "distinct_authors": 1, "top_author": "amy", "top_share": 1, "external_reviewers": 0, "never_reviewed": true, "dominated": true, "at_risk": true } ], "at_risk_files": ["src/solo.ts"], "summary": { "total_files": 2, "at_risk_count": 1, "single_author_count": 1, "never_reviewed_count": 1 } }
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.
npx -y @reneturcios/busfactor mcp
MCP client config:
{
"mcpServers": { "busfactor": { "command": "npx", "args": ["-y", "@reneturcios/busfactor", "mcp"] } } }
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; path is unique across the set, each authors entry is a {name, commits} pair with at least 1 commit, and reviewers lists 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 <= 1Returns {files, at_risk_files, summary}.
docker run -i ghcr.io/cloudcorprecords/busfactor
docker run --rm -v "$PWD:/w" ghcr.io/cloudcorprecords/busfactor analyze --input /w/args.json
npm install
npm run build # tsc -> dist/ npm test # tsx --test test/*.test.ts (pure local, no network) npm run dev # run the CLI from source
MIT — Copyright (c) 2026 Rene Turcios