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

Last 1 scan of this repo. Each new scan persists a full payload — historical comparison is exact, not lossy.

v1
Jun 16 00:43
v#IDStatusScoreGapsNodesCommitStarted
v scan_f520eaf5cfef ok 91.7 25 462 9dc4c9c v0.1.5 Jun 16 00:43
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.