io.github.icohangar-ops/codesentinel-mcp
NPM · @CUBICZAN/CODESENTINEL-MCP · SCANNED AUG 22
Codebase health MCP: dead code, cycles, coupling, architectural drift.
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 Security31
- Malware scan not yet available for this package.Unverified
- CVE check failed: a known high-severity CVE affects adm-zip 0.5.18, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 366 of 367 dependencies we could resolve, 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 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 Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 400 tokens (~66/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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 · @cubiczan/codesentinel-mcp
claude mcp add icohangar-ops-codesentinel-mcp -- npx -y @cubiczan/codesentinel-mcp
codex mcp add icohangar-ops-codesentinel-mcp -- npx -y @cubiczan/codesentinel-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"icohangar-ops-codesentinel-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@cubiczan/codesentinel-mcp"
],
"enabled": true
}
}
} openclaw mcp add icohangar-ops-codesentinel-mcp --command npx --arg -y --arg @cubiczan/codesentinel-mcp
mcp_servers:
icohangar-ops-codesentinel-mcp:
command: "npx"
args: ["-y", "@cubiczan/codesentinel-mcp"] {
"mcpServers": {
"icohangar-ops-codesentinel-mcp": {
"command": "npx",
"args": [
"-y",
"@cubiczan/codesentinel-mcp"
]
}
}
} 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.
- 22 Aug 26 48
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 22 Aug 2026 · Analysed npm/@cubiczan/codesentinel-mcp@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Vulnerabilities 14 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-8988-4f7v-96qf | CVE-2026-54285 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-45rx-2jwx-cxfr | CVE-2026-59892 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-xcpc-8h2w-3j85 | CVE-2026-39244 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-2pr8-phx7-x9h3 | CVE-2026-44294 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-66ff-xgx4-vchm | CVE-2026-44293 | high | yes | |
| GHSA-685m-2w69-288q | CVE-2026-44289 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-75px-5xx7-5xc7 | CVE-2026-44291 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-f38q-mgvj-vph7 | CVE-2026-54269 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-fx83-v9x8-x52w | CVE-2026-44292 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| GHSA-j3f2-48v5-ccww | CVE-2026-59877 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-jggg-4jg4-v7c6 | CVE-2026-45740 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-jvwf-75h9-cwgg | CVE-2026-44290 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-q6x5-8v7m-xcrf | CVE-2026-44288 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| GHSA-wcpc-wj8m-hjx6 | CVE-2026-48712 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Dependencies 366 packages
| Packages resolved | 366 |
|---|---|
| Stale | 97 |
| Tree resolution | Partial |
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_coupling ~65
Analyze coupling metrics across the codebase. Identifies modules with high fan-out (too many dependencies) and tightly coupled clusters.
| Name | Type | Req | Description |
|---|---|---|---|
| fan_out_threshold | number | – | Fan-out threshold for flagging modules |
| repo_path | string | – | Path or URL to the repository |
No output schema declared.
No examples provided.
analyze_dead_code ~75
Analyze a codebase for dead code — functions, classes, and modules that are defined but never referenced. Returns findings with file paths, line numbers, severity, and fix suggestions.
| Name | Type | Req | Description |
|---|---|---|---|
| include_suggestions | boolean | – | Whether to include fix suggestions |
| repo_path | string | – | Path or URL to the repository to analyze |
No output schema declared.
No examples provided.
detect_architectural_drift ~80
Detect architectural drift — violations of intended layer boundaries (e.g., UI importing from data layer, reverse dependencies).
| Name | Type | Req | Description |
|---|---|---|---|
| layers_config | string | – | JSON string defining layer patterns, e.g. {"ui": ["src/components/"], "data": ["src/db/"]} |
| repo_path | string | – | Path or URL to the repository |
No output schema declared.
No examples provided.
detect_circular_deps ~45
Detect circular dependencies between modules using DFS-based cycle detection. Returns cycles with involved files and impact assessment.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_path | string | – | Path or URL to the repository |
No output schema declared.
No examples provided.
explain_finding ~77
Get a detailed explanation of a specific code health finding, including why it matters, potential risks, and detailed remediation steps.
| Name | Type | Req | Description |
|---|---|---|---|
| codebase_context | string | – | Additional context about the codebase (language, framework, etc.) |
| finding_description | string | yes | Description of the specific finding to explain |
| finding_type | string | yes | – |
No output schema declared.
No examples provided.
full_health_scan ~58
Run a complete codebase health scan: dead code, circular dependencies, coupling metrics, and architectural drift. Returns an overall health score (0-100) and prioritized findings.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_path | string | – | Path or URL to the repository |
No output schema declared.
No examples provided.