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.
Sign up free Scan another repo

turbyho/fw-context-mcp

https://github.com/turbyho/fw-context-mcp · scanned 2026-06-16 00:43 UTC (2 months, 1 week ago)

25 raw signals (0 security + 25 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 25 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
91.7
/100
Security checks
92
0 findings
System graph
92
88.9% cov · 25 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 0 Medium 4 Low 18 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 25 Crowd 0 Layer: Software 11 Hardware 3 Frontend 1 Security 1 Cicd 1 Quality 8
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 91.7/100 with 88.9% coverage. It contains 462 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 25 findings — concentrated in software (11), quality (8), hardware (3). Risk profile is low: 0 critical, 0 high, 4 medium. Recommended next step: open the software layer findings first — that's where the highest-impact wins live.

Showing 22 of 25 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium System graph hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — src/fw_context_mcp/cli.py:386
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 70 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.11-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:1 containersPinned dependencies
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: src/fw_context_mcp/indexer/db.py:find_all_callers_recursive, src/fw_context_mcp/indexer/db.py:find_callees_recursive This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or doc…
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `file_id_old` in src/fw_context_mcp/indexer/ops.py:74
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: call_ollama
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/fw_context_mcp/llm/ollama.py:50
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_export
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/fw_context_mcp/cli.py:434
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_index
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/fw_context_mcp/cli.py:13
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_init
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/fw_context_mcp/cli.py:221
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_list
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/fw_context_mcp/cli.py:89
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_reset
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/fw_context_mcp/cli.py:117
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_search
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/fw_context_mcp/cli.py:60
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_status
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/fw_context_mcp/cli.py:160
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_watch
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/fw_context_mcp/cli.py:516
low System graph software Dead code conf 1.00 Possibly dead Python function: extract
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/fw_context_mcp/indexer/symbols.py:168
low System graph software Dead code conf 1.00 Possibly dead Python function: unit_is_unchanged
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/fw_context_mcp/indexer/ops.py:140
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph quality Complexity conf 1.00 Very large file: src/fw_context_mcp/mcp/server.py (1321 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/cb58d557-393b-4da3-b4ae-11772fdc1180/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/cb58d557-393b-4da3-b4ae-11772fdc1180/

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.