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.

thetwinnovators/FM-AI

https://github.com/thetwinnovators/FM-AI · scanned 2026-06-16 00:35 UTC (2 months, 2 weeks ago)

425 raw signals (0 security + 425 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 399 actionable findings from 1 signal source. 26 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 · 399 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 65 Medium 56 Low 88 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 399 Crowd 0 Layer: Frontend 108 Network 2 Security 9 Cicd 1 Quality 164 Api 115

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 93 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 (9 lines) in vite.config.js:66
info Commented-code block (5 lines) in vite-plugin-flowagent-sync.js:1
info Commented-code block (5 lines) in vite-plugin-daemon-info.js:362
info Commented-code block (12 lines) in vite-plugin-elevenlabs.js:9
info Commented-code block (7 lines) in cloudflare/plaid/worker.js:11
info Commented-code block (6 lines) in daemon/src/live-sky/service.ts:86
info Commented-code block (5 lines) in daemon/src/flow-trade/index.ts:210
info Commented-code block (6 lines) in src/python-curriculum/curriculum/python.ts:4
info Commented-code block (5 lines) in src/mcp/connectionContent.js:3
info Commented-code block (6 lines) in src/mcp/services/apiKeyTools.ts:3
info Commented-code block (6 lines) in src/mcp/storage/localMCPStorage.ts:19
info Commented-code block (5 lines) in src/components/settings/ApiServiceCards.jsx:3

View all commented-out code findings →

Config drift 7 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.

7 matching findings on this repo

medium Insecure pattern 'node_child_process' in daemon/src/config.ts:3 daemon/src/config.ts:3
info Commented-code block (9 lines) in vite.config.js:66
info Commented-code block (5 lines) in src/lib/higgsfieldConfig.js:1
low Old/deprecated-named symbol `eleven_multilingual_v2` in src/lib/voice/voiceConf…
info Commented-code block (8 lines) in src/lib/search/rankingConfig.js:4
info Commented-code block (5 lines) in src/lib/search/searchConfig.js:12
info Commented-code block (7 lines) in src/lib/llm/ollamaConfig.js:62

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/dd577c7a-9738-4d0a-a74e-dba0ea2eb42e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/dd577c7a-9738-4d0a-a74e-dba0ea2eb42e/

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.