RepoRipple
PYPI · REPORIPPLE · SCANNED OCT 1
Deterministic repository change-impact analysis for engineers and coding agents.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to adiarora06/RepoRipple). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 201 tokens (~100/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the RepoRipple MCP server?
RepoRipple runs locally as a PyPI package, launched with uvx reporipple. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · reporipple
claude mcp add adiarora06-reporipple -- uvx reporipple
{
"mcpServers": {
"adiarora06-reporipple": {
"command": "uvx",
"args": [
"reporipple"
]
}
}
} {
"servers": {
"adiarora06-reporipple": {
"command": "uvx",
"args": [
"reporipple"
]
}
}
} codex mcp add adiarora06-reporipple -- uvx reporipple
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"adiarora06-reporipple": {
"type": "local",
"command": [
"uvx",
"reporipple"
],
"enabled": true
}
}
} openclaw mcp add adiarora06-reporipple --command uvx --arg reporipple
mcp_servers:
adiarora06-reporipple:
command: "uvx"
args: ["reporipple"] {
"McpServers": {
"adiarora06-reporipple": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"reporipple"
]
}
}
} assistant mcp add adiarora06-reporipple -t stdio -c uvx -a reporipple
{
"mcpServers": {
"adiarora06-reporipple": {
"command": "uvx",
"args": [
"reporipple"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Sept 26 +2
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.10 ▲ functional
- Package version: 0.2.0 → 0.3.0 functional
- 29 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 28 Sept 26 +25
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 55
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 1 Oct 2026 · Analysed pypi/reporipple@0.3.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | adiarora06/RepoRipple |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/adiarora06/RepoRipple/.github/workflows/release.yml@refs/tags/v0.3.0 |
| Rekor log index | 3023708116 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:ca67833bd158bb32011893443f89877c10c6cea54960940408639aa9dca159b8 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_worktree Analyze current Git changes ~79
Analyze worktree changes, or compare HEAD with an optional Git base revision.
| Name | Type | Req | Description |
|---|---|---|---|
| base | – | – | Optional Git revision to compare with HEAD. |
| max_depth | integer | – | Maximum reverse-dependency traversal depth. |
| repository | string | – | Repository directory, relative to the server's allowed root. Absolute paths are accepted only when they remain inside that root. |
| Name | Type | Req | Description |
|---|---|---|---|
| changed_files | array | yes | – |
| documentation_to_review | array | yes | – |
| graph_edges | integer | yes | – |
| graph_files | integer | yes | – |
| impacted_files | array | yes | – |
| repository | string | yes | – |
| risk_level | string | yes | – |
| risk_reasons | array | yes | – |
| suggested_tests | array | yes | – |
| warnings | array | yes | – |
No examples provided.
forecast_change Forecast a code change ~78
Estimate the blast radius of proposed repository-relative file changes.
| Name | Type | Req | Description |
|---|---|---|---|
| changed_files | array | yes | Repository-relative files that are expected to change. |
| max_depth | integer | – | Maximum reverse-dependency traversal depth. |
| repository | string | – | Repository directory, relative to the server's allowed root. Absolute paths are accepted only when they remain inside that root. |
| Name | Type | Req | Description |
|---|---|---|---|
| changed_files | array | yes | – |
| documentation_to_review | array | yes | – |
| graph_edges | integer | yes | – |
| graph_files | integer | yes | – |
| impacted_files | array | yes | – |
| repository | string | yes | – |
| risk_level | string | yes | – |
| risk_reasons | array | yes | – |
| suggested_tests | array | yes | – |
| warnings | array | yes | – |
No examples provided.
What is the RepoRipple MCP server?
RepoRipple is an MCP server listed in the public MCP registry as io.github.adiarora06/reporipple. Deterministic repository change-impact analysis for engineers and coding agents. This page covers its PyPI package (reporipple).
Is the RepoRipple MCP server safe to use?
RepoRipple scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 1 October 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the RepoRipple MCP server expose?
RepoRipple exposes 2 tools: forecast_change, analyze_worktree. Their descriptions and schemas cost roughly 157 tokens of context every time the server is loaded.
Is the RepoRipple MCP server still maintained?
RepoRipple is still listed as active in the MCP registry. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the RepoRipple MCP server under?
RepoRipple declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.