Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

theshadow27/mcp-cli

https://github.com/theshadow27/mcp-cli · scanned 2026-06-16 00:34 UTC (2 months, 2 weeks ago)

338 raw signals (0 security + 338 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 323 actionable findings from 1 signal source. 15 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 323 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 6 High 74 Medium 86 Low 102 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 323 Crowd 0 Layer: Frontend 69 Security 42 Cicd 3 Quality 142 Api 67

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Commented-out code 54 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (6 lines) in test/harness.ts:64
info Commented-code block (5 lines) in test/daemon-integration.spec.ts:487
info Commented-code block (5 lines) in test/transport-errors.spec.ts:24
info Commented-code block (6 lines) in test/mock-claude.ts:15
info Commented-code block (5 lines) in scripts/check-coverage.ts:218
info Commented-code block (5 lines) in scripts/doing-it-wrong.ts:79
info Commented-code block (6 lines) in scripts/daemon-workers.spec.ts:42
info Commented-code block (10 lines) in scripts/build.ts:138
info Commented-code block (6 lines) in scripts/am-i-done.ts:143
info Commented-code block (5 lines) in scripts/rules/no-import-cycles.rule.spec.ts:2…
info Commented-code block (5 lines) in scripts/rules/no-raw-path-handling.rule.ts:52
info Commented-code block (5 lines) in scripts/rules/fixtures/no-raw-path-handling__…

View all commented-out code findings →

Config drift 4 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

4 matching findings on this repo

medium Runtime service client appears to use placeholder configuration
high Agent instruction/config may expose a secret: .claude/diary/20260312.md .claude/diary/20260312.md:78
high Agent instruction/config may expose a secret: .claude/memory/feedback_quota_sta… .claude/memory/feedback_quota_status_staleness.md:14
high Agent instruction/config may expose a secret: .claude/memory/feedback_phase_rep… .claude/memory/feedback_phase_repair_to_qa.md:10

View all config drift findings →

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/67e53a5f-fde4-4448-baab-939f4b580a01/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/67e53a5f-fde4-4448-baab-939f4b580a01/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.