RepoRipple
Know what a code change can break before you merge it.
Усильте агента
Собственная команда издателя. Не эндпоинт PlugMCP.
Host a copy with our keys and logs.
uvx reporipple==0.6.0У Claude Code нет ссылки для установки локальной команды. Скопируйте команду ниже и выполните её в терминале.
claude mcp add io.github.adiarora06-reporipple -- uvx reporipple==0.6.0Выполните в терминале.
{ "mcpServers": { "io.github.adiarora06-reporipple": { "command": "uvx", "args": [ "reporipple==0.6.0" ] } }}claude_desktop_config.json
Удалённый URL или команда на вашем компьютере? Чем различаются два способа установки
Запустить на PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
ЗапускRepoRipple is a local-first change-impact analyzer for engineers and coding agents. It builds a lightweight dependency graph from a repository, reads the current Git diff, traces reverse dependencies, recommends relevant tests, and emits a review-ready Markdown or JSON report.
The deterministic analyzer requires no API key, hosted service, source upload, or framework integration. An optional, explicitly requested OpenRouter explanation can turn its anonymized evidence into a short narrative without changing the underlying analysis.
Code graphs explain how a repository is connected. RepoRipple applies that graph to the change in front of you:
pip install reporipple
# Analyze staged, unstaged, and untracked changes.
reporipple .
# Compare a feature branch with main.
reporipple . --base origin/main
# Generate machine-readable context for an agent or automation.
reporipple . --base origin/main --format json --output impact.json
# Fail CI when a change reaches high risk.
reporipple . --base origin/main --fail-on high
# Audit the exact anonymized OpenRouter request without sending it.
reporipple . --base origin/main --explain-preview
Run it once without installing:
uvx reporipple . --base origin/main
Add RepoRipple to a pull-request workflow to create Markdown and JSON impact reports and append the Markdown report to the GitHub job summary:
name: RepoRipple
on:
pull_request:
permissions:
contents: read
jobs:
impact:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
fetch-depth: 0
persist-credentials: false
- id: reporipple
uses: adiarora06/RepoRipple@6253b03f91e46c2f38fb2e05958dbc174d6a08d7 # v0.4.0
with:
base: ${{ github.event.pull_request.base.sha }}
- uses: actions/upload-artifact@cf430e030ddbb5b0abf93d22962f4752f3646cd9 # v7.0.2
with:
name: reporipple-impact
path: |
${{ steps.reporipple.outputs.markdown-report }}
${{ steps.reporipple.outputs.json-report }}
The Action accepts path, base, max-depth, fail-on, and reports-directory. It outputs
markdown-report, json-report, and risk-level. For reproducible builds, pin RepoRipple to a
release commit SHA and use fetch-depth: 0 so the requested base revision is available.
This repository's own pull-request workflow demonstrates a fork-safe commenting design. Analysis runs with read-only contents access. A separate job updates one stable RepoRipple comment only for branches in the same repository; fork pull requests keep their report in the job summary and downloadable artifact without receiving a write-capable token.
RepoRipple can expose the same deterministic analysis to Codex, OpenCode, Cursor, Claude Code, and VS Code over a local, read-only MCP server. From a source checkout:
uv run reporipple mcp --root /path/to/allowed/workspace
Launch the published package without a clone:
uvx reporipple mcp --root /path/to/allowed/workspace
The server provides forecast_change for proposed edits and analyze_worktree for
actual Git changes. See the
MCP setup guide for
client-specific commands and configuration.
The architecture guide explains how the CLI, GitHub Action, MCP server, and optional explanation layer share one deterministic analysis engine.
# RepoRipple impact report: checkout-service
**Risk:** `high` · **Graph:** 84 files / 137 dependency edges
## Changed files
- `src/billing/store.py`
## Impacted files
- `src/billing/service.py` — distance 1 via `store.py` → `service.py`
- `src/api/checkout.py` — distance 2 via `store.py` → `service.py` → `checkout.py`
## Suggested verification
- `tests/test_billing_service.py`
- `tests/test_checkout.py`
tsconfig.json or jsconfig.json paths mappings, its baseUrl, and then npm/Yarn workspace
packages declared by the root package.json.Configuration-only changes now produce a concrete blast radius. Each JS/TS source is linked to its
nearest tsconfig.json or jsconfig.json, that configuration's local extends chain, and its
nearest live package.json. When Git supplies a deleted or renamed manifest, RepoRipple retains
the nearest historical package boundary below the current live boundary as a second impact target
without letting it shadow that live ancestor. A deleted project config likewise remains an impact
target but cannot supply aliases or baseUrl for the current tree, including when a live config
still names it in extends. For extensionless extends, a live fallback is preferred while a
deleted candidate remains direct historical metadata. Deleted config chains are not traversed;
this prevents stale history from consuming work needed for the live graph. Successfully matched
workspace imports are additionally linked to the root workspace manifest and the imported
package's manifest; unrelated external imports are not. Changing any of that metadata reports
directly governed or dependent source files first, then continues through their downstream
importers. Metadata remains outside the source-file inventory, while its deterministic
relationships are included in the reported graph edge count.
Workspace resolution is local and source-aware. RepoRipple matches imports to explicitly declared
package.json workspaces by package name, respects their public export boundaries, and follows
entry points that resolve to source files in the repository. Workspace globs support recursive
patterns, bounded brace alternatives and ranges, and exclusions. Conditional exports distinguish
ES module and CommonJS entry points: .mts/.mjs use the import profile, .cts/.cjs use the
require profile, and ambiguous TypeScript/JavaScript files conservatively inspect both. RepoRipple
also keeps applicable custom conditions declared before a syntax or default fallback so it does
not silently miss browser, platform, or source-only dependency edges.
Custom conditions are evaluated without assuming one runtime condition set. Nested or repeated custom conditions can therefore produce conservative extra edges that no single runtime would select; impact analysis favors that visible over-approximation over silently missing a dependent.
RepoRipple does not inspect installed node_modules, contact a registry, or run a package manager.
pnpm-workspace.yaml, external packages, and workspace entry points that exist only as ignored or
missing build output are not currently resolved. Pathological workspace glob sets that exceed the
resolver's fixed safety budgets fail closed instead of consuming unbounded scan time. The current
limits are 512 effective patterns, 2,048 aggregate path components across unique patterns, 64 KiB
of raw patterns, and 256 KiB after brace expansion. Project-config traversal is limited to 16
levels, 64 loaded config nodes per root resolution, and 64 config metadata dependencies per
source. A repository scan stores at most 100,000 unique source-to-metadata relationships. Scan
warnings identify every exceeded limit, and completed top-level config resolutions are reused
without bypassing cycle or depth checks inside an extends traversal. Loaded live config paths
have priority in the per-source metadata cap; skipped live targets are next, and direct historical
targets use the remaining capacity. Changes to tsconfig.json, jsconfig.json, and package
manifests are both flagged as configuration risk and traced through their governed or dependent
JS/TS files. Deleted and renamed metadata uses the same bounded in-memory Git overlay as deleted
source. For an in-place workspace-manifest edit that removes an old package name entirely,
RepoRipple can still report files owned by that package, but cannot reconstruct importers of the
removed name without a second full historical scan.
The core intentionally avoids LLM scoring. Results stay reproducible, private, fast, and usable in CI. Optional AI explanations can be layered over the JSON output without making correctness depend on a model.
AI explanation is off by default and is activated only by --explain. The deterministic risk level, evidence, report, and --fail-on exit status remain authoritative even if OpenRouter is unavailable or returns an invalid response.
First inspect the exact key-free body that would leave your machine:
reporipple /path/to/repository --base main --explain-preview
The preview does not read an API key and does not make a network request. When you are satisfied with the payload, provide the key through the environment and explicitly request an explanation:
export OPENROUTER_API_KEY="your-key"
reporipple /path/to/repository --base main --explain
There is no command-line key option and RepoRipple does not read a key from a file. The integration uses only the Python standard library and applies all of these controls to every request:
E001; returned IDs are schema-validated and mapped back to labels locally.zdr: true), denies data collection, and selects only providers that support every requested parameter.The pinned default model is openai/gpt-6-luna. Override it with --explain-model or
REPORIPPLE_OPENROUTER_MODEL; privacy, schema, and price controls remain mandatory. Privacy
filters may reduce provider availability, and the request fails closed when no eligible provider
satisfies them. OpenRouter's ZDR policy prevents eligible providers from retaining prompts and
responses after processing; it does not mean the request stays on your machine. See OpenRouter's
structured outputs,
ZDR controls, and
provider routing controls.
reporipple [PATH]
--version show the installed RepoRipple version and exit
--base REVISION compare REVISION...HEAD
--changed PATH analyze an explicit path; repeat as needed
--max-depth N reverse dependency traversal depth (default: 4)
--format markdown|json
--output FILE
--fail-on medium|high
--explain request an optional privacy-filtered OpenRouter explanation
--explain-preview show the exact sanitized request without sending it
--explain-model NAME use a pinned provider/model slug for either explanation mode
reporipple mcp
--root PATH restrict tool access to PATH and its descendants
When no base or explicit path is supplied, RepoRipple analyzes staged, unstaged, and untracked files. On a clean checkout it falls back to the latest commit.
--explain and --explain-preview are mutually exclusive. With JSON output, either flag returns a wrapper containing deterministic_report plus the explanation or preview; ordinary JSON output is unchanged.
uv venv --python 3.12
uv pip install --python .venv/bin/python -e ".[dev]"
.venv/bin/ruff check .
.venv/bin/pytest
uv build
RepoRipple's deterministic analysis runs locally and does not transmit repository contents. It
invokes Git using argument arrays rather than a shell and reads only supported, non-symlinked
source files outside common generated and dependency directories. The MCP server constrains every
repository request to its configured --root and exposes read-only tools only. Network access
occurs only when --explain is present; --explain-preview remains fully local so the outbound
body can be audited first.
MIT
Deterministic repository change-impact analysis for engineers and coding agents.
{ "mcpServers": { "io.github.adiarora06-reporipple": { "command": "uvx", "args": [ "reporipple==0.6.0" ] } }}Инструменты
Списка инструментов пока нет. У удалённых серверов он появляется после первой проверки состояния.
FAQ
Скопируйте на этой странице конфигурацию stdio для Cursor, Claude Desktop, Claude Code или VS Code. Она использует установку издателя, а не прокси PlugMCP.
В этой записи не указано обязательных переменных окружения.
RepoRipple работает локально через stdio.
Последняя проверка: 2026-11-15. Deterministic repository change-impact analysis for engineers and coding agents.