E
error-path/opendrs
A calibrated 0-1 risk score for every pull request, so AI-reviewed, low-blast-radius PRs can be
★ 3·更新 2026-11-17
在 GitHub 查看 ↗直链 · 无中转页
我们没有从该仓库取到可核对的安装命令,也没有公开的远端端点。这两样都没有时,我们不出配置——编一条出来比不给更糟。 各客户端的接法 →
- ★ 数取值
- 3 ★ · error-path/opendrs · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 3 ★ · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
error-path/opendrs;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# opendrs: PR blast radius analyzer and risk score for safe auto-approval
以下摘录自该仓库的 README(片段)
A calibrated 0-1 risk score for every pull request, so AI-reviewed, low-blast-radius PRs can be
auto-approved into the merge queue while risky ones still wait for a human.
AI agents now write and review code faster than people can read it, so human review has become
the bottleneck. Most pull requests are low risk, and a few cause most incidents. opendrs measures
each PR's blast radius and risk: what the change touches, how many files depend on it, the
history of the files it changes, author experience, missing tests and critical paths. It turns
that into a 0-1 score using signals from your own git history. A team then sets a policy.
For example, a PR that scores below 0.3 and has passed an AI review (Claude, CodeRabbit, Copilot
or any check run) is approved and sent to the merge queue or auto-merge. Riskier PRs still wait
for a human. The approach follows Meta's Diff Risk Score (DRS); opendrs is an independent,
open-source implementation that runs in any git repository, with no service to host.
Contents: Install · Quick start · How it works ·
Features · Results · CLI and MCP ·
Documentation · Limitations ·
Compared with other tools · Prior art
## Install
| Use it as | Command | Details |
| GitHub Action | uses: error-path/opendrs@v0 (Marketplace) | Comments, labels and, optionally, approves and merges. GitHub Action reference |
| CLI | npx @error-path/opendrs score | CLI, MCP server, Claude Code plugin and agent skill |
| MCP server (any agent) | npx -y @error-path/opendrs mcp | Tools: score_diff, explain_file_risk, list_hotspots, suggest_reviewers |
| Claude Code plugin (skill plus MCP server) | /plugin marketplace add error-path/opendrs, then /plugin install opendrs@opendrs | |
| Agent skill (Claude Code, Cursor, Codex and others) | npx skills add error-path/opendrs | plugin/skills/opendrs/SKILL.md |
| Docker (MCP server over stdio) | docker build -t opendrs . && docker run -i --rm -v "$PWD:/repo" opendrs | Mount the repository to score at /repo |
Website and guides: error-path.github.io/opendrs.
## Quick start
Score your current branch against the default branch. No configuration or API key is needed:
sh
npx @error-path/opendrs score
You get a score, a tier (green, yellow or red), the signals that drove it with their evidence,
and the policy decision. --json prints the full result, and --fail-above 0.6 makes the
command exit 1 above a threshold.
To score every pull request, add .github/workflows/opendrs.yml (or run npx @error-path/opendrs init):
yaml
name: opendrs
on:
pull_request:
types: [opened, synchronize, reopened, ready_for_review, labeled, unlabeled]
permissions:
contents: read
pull-requests: write
checks: read
jobs:
opendrs:
runs-on: ubuntu-latest
steps:
uses: actions/checkout@v5
with:
fetch-depth: 0 # required: the score reads past commits and authors
uses: error-path/opendrs@v0
This only comments and labels. Approval is off until you turn it on in .opendrs.yml on your
default branch; see how to auto-approve low-risk PRs and the
GitHub Action reference.
## How it works
mermaid
flowchart LR
diff["git diff merge-base...head"] --> signals
hist["git history"] --> signals
imports["import graph"] --> signals
llm["LLM judge (optional)"] --> signals
auto-approved into the merge queue while risky ones still wait for a human.
AI agents now write and review code faster than people can read it, so human review has become
the bottleneck. Most pull requests are low risk, and a few cause most incidents. opendrs measures
each PR's blast radius and risk: what the change touches, how many files depend on it, the
history of the files it changes, author experience, missing tests and critical paths. It turns
that into a 0-1 score using signals from your own git history. A team then sets a policy.
For example, a PR that scores below 0.3 and has passed an AI review (Claude, CodeRabbit, Copilot
or any check run) is approved and sent to the merge queue or auto-merge. Riskier PRs still wait
for a human. The approach follows Meta's Diff Risk Score (DRS); opendrs is an independent,
open-source implementation that runs in any git repository, with no service to host.
Contents: Install · Quick start · How it works ·
Features · Results · CLI and MCP ·
Documentation · Limitations ·
Compared with other tools · Prior art
## Install
| Use it as | Command | Details |
| GitHub Action | uses: error-path/opendrs@v0 (Marketplace) | Comments, labels and, optionally, approves and merges. GitHub Action reference |
| CLI | npx @error-path/opendrs score | CLI, MCP server, Claude Code plugin and agent skill |
| MCP server (any agent) | npx -y @error-path/opendrs mcp | Tools: score_diff, explain_file_risk, list_hotspots, suggest_reviewers |
| Claude Code plugin (skill plus MCP server) | /plugin marketplace add error-path/opendrs, then /plugin install opendrs@opendrs | |
| Agent skill (Claude Code, Cursor, Codex and others) | npx skills add error-path/opendrs | plugin/skills/opendrs/SKILL.md |
| Docker (MCP server over stdio) | docker build -t opendrs . && docker run -i --rm -v "$PWD:/repo" opendrs | Mount the repository to score at /repo |
Website and guides: error-path.github.io/opendrs.
## Quick start
Score your current branch against the default branch. No configuration or API key is needed:
sh
npx @error-path/opendrs score
You get a score, a tier (green, yellow or red), the signals that drove it with their evidence,
and the policy decision. --json prints the full result, and --fail-above 0.6 makes the
command exit 1 above a threshold.
To score every pull request, add .github/workflows/opendrs.yml (or run npx @error-path/opendrs init):
yaml
name: opendrs
on:
pull_request:
types: [opened, synchronize, reopened, ready_for_review, labeled, unlabeled]
permissions:
contents: read
pull-requests: write
checks: read
jobs:
opendrs:
runs-on: ubuntu-latest
steps:
uses: actions/checkout@v5
with:
fetch-depth: 0 # required: the score reads past commits and authors
uses: error-path/opendrs@v0
This only comments and labels. Approval is off until you turn it on in .opendrs.yml on your
default branch; see how to auto-approve low-risk PRs and the
GitHub Action reference.
## How it works
mermaid
flowchart LR
diff["git diff merge-base...head"] --> signals
hist["git history"] --> signals
imports["import graph"] --> signals
llm["LLM judge (optional)"] --> signals
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/error-path-opendrs/)
- 来源
- awesome · https://github.com/error-path/opendrs
- 按领域浏览
- MCP 服务
- Traction
- 3 ★
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。