io.github.vineethwilson15/semamerge
NPM · SEMAMERGE · SCANNED AUG 3
Detects semantic merge conflicts between Git branches using AST-level analysis
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (102 of 106), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (102 of 106), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 99 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 358 tokens (~89/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · semamerge
claude mcp add vineethwilson15-semamerge -- npx -y semamerge
codex mcp add vineethwilson15-semamerge -- npx -y semamerge
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vineethwilson15-semamerge": {
"type": "local",
"command": [
"npx",
"-y",
"semamerge"
],
"enabled": true
}
}
} openclaw mcp add vineethwilson15-semamerge --command npx --arg -y --arg semamerge
mcp_servers:
vineethwilson15-semamerge:
command: "npx"
args: ["-y", "semamerge"] {
"mcpServers": {
"vineethwilson15-semamerge": {
"command": "npx",
"args": [
"-y",
"semamerge"
]
}
}
} 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.
- 3 Aug 26 +3
- Stability: unverified → 0.23 ▲ functional
- 2 Aug 26 +44
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- Licence: MIT functional
- 1 Aug 26 +15
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 −40
- Malware scan: pass → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- 30 Jul 26 +22
- Tool coverage: unverified → 100 ▲ functional
- 28 Jul 26 −22
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 46
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 102 packages
102 packages in the resolved dependency tree · 102 deprecated · 31 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
analyze_branches ~91
Deep semantic analysis between two branches. Returns a detailed per-file report of all semantic changes and conflicts, including cross-file dependency issues.
| Name | Type | Req | Description |
|---|---|---|---|
| baseBranch | string | — | Common base branch (auto-detected if not provided) |
| branchA | string | yes | First branch to compare |
| branchB | string | yes | Second branch to compare |
| repoPath | string | yes | Absolute path to the Git repository |
No output schema declared.
No examples provided.
analyze_file_pair ~82
Deep-dive semantic diff of a single file between two branches. Shows exactly what each branch changed and where conflicts arise.
| Name | Type | Req | Description |
|---|---|---|---|
| branchA | string | yes | First branch |
| branchB | string | yes | Second branch |
| filePath | string | yes | Path to the file within the repository |
| repoPath | string | yes | Absolute path to the Git repository |
No output schema declared.
No examples provided.
check_merge_safety ~96
Quick pre-merge safety check. Analyzes two branches for semantic conflicts that Git would miss (signature changes, removed exports, parameter mismatches, etc.). Returns a risk score: safe/warning/danger.
| Name | Type | Req | Description |
|---|---|---|---|
| repoPath | string | yes | Absolute path to the Git repository |
| sourceBranch | string | yes | The branch being merged (source) |
| targetBranch | string | yes | The branch being merged into (target) |
No output schema declared.
No examples provided.
list_semantic_changes ~89
Lists all semantic changes on a branch (function additions/removals, export changes, type changes, etc.) relative to a base. Useful for understanding what semantically changed.
| Name | Type | Req | Description |
|---|---|---|---|
| baseBranch | string | — | Base branch to compare against (defaults to merge-base with HEAD) |
| branch | string | yes | Branch to analyze |
| repoPath | string | yes | Absolute path to the Git repository |
No output schema declared.
No examples provided.