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

BigBodyCobain/Shadowbroker

https://github.com/BigBodyCobain/Shadowbroker · scanned 2026-06-17 01:23 UTC (1 month, 2 weeks ago)

406 raw signals (0 security + 406 graph)

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

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -24.3 (diff) · 379 actionable findings from 1 signal source. 27 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
52.4
/100
Security checks
52
0 findings
System graph
52
100.0% cov · 379 findings
Critical
1
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 1 High 46 Medium 50 Low 186 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 379 Crowd 0 Layer: Software 22 Frontend 36 Hardware 5 Security 53 Cicd 3 Quality 208 Api 52
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 52.4/100 with 100.0% coverage. It contains 12204 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 406 findings — concentrated in quality (226), security (54), api (52). Risk profile is high: 2 critical, 46 high, 58 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 282 of 379 actionable findings. 406 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical System graph security Secrets conf 1.00 2 occurrences Possible secret in desktop-shell/tauri-skeleton/build.sh
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 48, 136
desktop-shell/tauri-skeleton/build.sh:48, 136 (2 hits)
high System graph quality Integrity conf 1.00 Blocking `requests.get(...)` inside `async def telegram_media_proxy` — backend/routers/intel_feeds.py:97
Sync I/O inside an async function blocks the event loop. While `requests.get(...)` is running, *all* other coroutines on this loop are paused — silent throughput collapse under concurrency. Use the async equivalent (`httpx.AsyncClient`, `asyncio.sleep`, `aiofiles`) or wrap with `await asyncio.to_th…
backend/routers/intel_feeds.py:97 Sync io in asyncPerformance
high System graph quality Integrity conf 1.00 Blocking `time.sleep(...)` inside `async def lifespan` — backend/main.py:2728
Sync I/O inside an async function blocks the event loop. While `time.sleep(...)` is running, *all* other coroutines on this loop are paused — silent throughput collapse under concurrency. Use the async equivalent (`httpx.AsyncClient`, `asyncio.sleep`, `aiofiles`) or wrap with `await asyncio.to_thre…
backend/main.py:2728 Sync io in asyncPerformance
high System graph quality Integrity conf 1.00 Blocking `time.sleep(...)` inside `async def lifespan` — backend/main.py:2739
Sync I/O inside an async function blocks the event loop. While `time.sleep(...)` is running, *all* other coroutines on this loop are paused — silent throughput collapse under concurrency. Use the async equivalent (`httpx.AsyncClient`, `asyncio.sleep`, `aiofiles`) or wrap with `await asyncio.to_thre…
backend/main.py:2739 Sync io in asyncPerformance
high System graph quality Integrity conf 1.00 Blocking `time.sleep(...)` inside `async def lifespan` — backend/main.py:2741
Sync I/O inside an async function blocks the event loop. While `time.sleep(...)` is running, *all* other coroutines on this loop are paused — silent throughput collapse under concurrency. Use the async equivalent (`httpx.AsyncClient`, `asyncio.sleep`, `aiofiles`) or wrap with `await asyncio.to_thre…
backend/main.py:2741 Sync io in asyncPerformance
high System graph quality Integrity conf 1.00 Blocking `time.sleep(...)` inside `async def lifespan` — backend/main.py:2812
Sync I/O inside an async function blocks the event loop. While `time.sleep(...)` is running, *all* other coroutines on this loop are paused — silent throughput collapse under concurrency. Use the async equivalent (`httpx.AsyncClient`, `asyncio.sleep`, `aiofiles`) or wrap with `await asyncio.to_thre…
backend/main.py:2812 Sync io in asyncPerformance
high System graph api Wiring conf 1.00 Dangling fetch: GET /data/submarine-cables.json (frontend/src/components/MaplibreViewer.tsx:1183)
`frontend/src/components/MaplibreViewer.tsx:1183` calls `GET /data/submarine-cables.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/data/submarine-cables.json` If this points at an external API, prefix it with …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:3000/api/wormhole/identity/bootstrap (frontend/src/app/api/[...path]/route.ts:155)
`frontend/src/app/api/[...path]/route.ts:155` calls `GET http://localhost:3000/api/wormhole/identity/bootstrap` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:3000/api/wormhole/identity/bootstrap` If…
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI POST `analyze_road_corridor_here` without auth dependency — backend/routers/road_corridors.py:64
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/road_corridors.py:64 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `api_wikidata_sparql` without auth dependency — backend/routers/tools.py:108
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/tools.py:108 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `api_wormhole_leave` without auth dependency — backend/routers/wormhole.py:666
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/wormhole.py:666 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `append_event` without auth dependency — backend/routers/infonet.py:493
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/infonet.py:493 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `dm_block` without auth dependency — backend/routers/mesh_dm.py:410
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/mesh_dm.py:410 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `dm_count_secure` without auth dependency — backend/routers/mesh_dm.py:383
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/mesh_dm.py:383 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `dm_key_witness` without auth dependency — backend/routers/mesh_dm.py:449
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/mesh_dm.py:449 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `dm_poll_secure` without auth dependency — backend/routers/mesh_dm.py:356
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/mesh_dm.py:356 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `dm_prekey_peer_lookup` without auth dependency — backend/routers/mesh_dm.py:299
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/mesh_dm.py:299 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `dm_register_key` without auth dependency — backend/routers/mesh_dm.py:235
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/mesh_dm.py:235 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `dm_replicate_envelope` without auth dependency — backend/routers/mesh_peer_sync.py:99
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/mesh_peer_sync.py:99 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `dm_send` without auth dependency — backend/routers/mesh_dm.py:349
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/mesh_dm.py:349 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `gate_create` without auth dependency — backend/routers/mesh_public.py:1379
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/mesh_public.py:1379 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `gate_message` without auth dependency — backend/routers/mesh_public.py:1466
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/mesh_public.py:1466 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `gate_peer_pull` without auth dependency — backend/routers/mesh_peer_sync.py:275
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/mesh_peer_sync.py:275 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `gate_peer_push` without auth dependency — backend/routers/mesh_peer_sync.py:157
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/mesh_peer_sync.py:157 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `infonet_peer_push` without auth dependency — backend/routers/mesh_peer_sync.py:64
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/mesh_peer_sync.py:64 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `infonet_sync_post` without auth dependency — backend/routers/mesh_public.py:1553
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/mesh_public.py:1553 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `mesh_identity_revoke` without auth dependency — backend/routers/mesh_public.py:1314
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/mesh_public.py:1314 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `mesh_identity_rotate` without auth dependency — backend/routers/mesh_public.py:1229
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/mesh_public.py:1229 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `mesh_report` without auth dependency — backend/routers/mesh_public.py:1125
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/mesh_public.py:1125 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `mesh_send` without auth dependency — backend/routers/mesh_public.py:617
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/mesh_public.py:617 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `mesh_vote` without auth dependency — backend/routers/mesh_public.py:1053
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/mesh_public.py:1053 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `oracle_predict` without auth dependency — backend/routers/mesh_oracle.py:69
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/mesh_oracle.py:69 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `oracle_stake` without auth dependency — backend/routers/mesh_oracle.py:265
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/mesh_oracle.py:265 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `osint_sweep_scan` without auth dependency — backend/routers/osint.py:142
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/osint.py:142 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `preview_petition_payload` without auth dependency — backend/routers/infonet.py:173
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/infonet.py:173 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `satellite_overflights` without auth dependency — backend/routers/data.py:886
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/data.py:886 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trust_vouch` without auth dependency — backend/routers/mesh_dm.py:514
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/mesh_dm.py:514 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `validate_event` without auth dependency — backend/routers/infonet.py:190
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/infonet.py:190 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `set_gate_envelope_policy` without auth dependency — backend/routers/mesh_public.py:1924
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/mesh_public.py:1924 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `set_gate_legacy_envelope_fallback` without auth dependency — backend/routers/mesh_public.py:1953
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/routers/mesh_public.py:1953 securityAuth fastapi unauth mutation
high System graph security security conf 1.00 Insecure pattern 'eval_used' in backend/services/infonet/governance/dsl_executor.py:193
Found a known-risky pattern (eval_used). Review and replace if possible.
backend/services/infonet/governance/dsl_executor.py:193 Eval used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in backend/services/infonet/governance/dsl_executor.py:194
Found a known-risky pattern (exec_used). Review and replace if possible.
backend/services/infonet/governance/dsl_executor.py:194 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in desktop-shell/src/handlers/settingsHandlers.ts:15
Found a known-risky pattern (exec_used). Review and replace if possible.
desktop-shell/src/handlers/settingsHandlers.ts:15 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in desktop-shell/src/handlers/updateHandlers.ts:6
Found a known-risky pattern (exec_used). Review and replace if possible.
desktop-shell/src/handlers/updateHandlers.ts:6 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in desktop-shell/src/handlers/wormholeHandlers.ts:25
Found a known-risky pattern (exec_used). Review and replace if possible.
desktop-shell/src/handlers/wormholeHandlers.ts:25 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in frontend/src/components/MeshTerminal.tsx:4807
Found a known-risky pattern (exec_used). Review and replace if possible.
frontend/src/components/MeshTerminal.tsx:4807 Exec used
high System graph security security conf 1.00 Insecure pattern 'python_os_system' in backend/services/infonet/governance/dsl_executor.py:202
Found a known-risky pattern (python_os_system). Review and replace if possible.
backend/services/infonet/governance/dsl_executor.py:202 Python os system
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/app/api/[...path]/route.ts:34
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/components/AIIntelPanel.tsx:479
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/components/InfonetTerminal/AIQueryView.tsx:140
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/components/InfonetTerminal/GateView.tsx:484
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/components/InfonetTerminal/MarketView.tsx:175
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/components/map/panels/SigintPanels.tsx:96
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/components/MaplibreViewer.tsx:485
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/components/MeshChat/useMeshChatController.ts:1155
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/components/MeshTerminal.tsx:2067
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/components/NewsFeed.tsx:407
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/components/PredictionsPanel.tsx:698
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/components/RadioInterceptPanel.tsx:87
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/components/ReconPanel.tsx:76
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/components/ShodanPanel.tsx:576
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/components/TimelinePanel.tsx:120
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/hooks/useDataPolling.ts:180
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/hooks/useLiveUamapScraperOptIn.ts:42
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/hooks/usePredictionMarketsOptIn.ts:38
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/hooks/useRegionDossier.ts:87
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/lib/aiIntelClient.ts:32
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/lib/localControlTransport.ts:106
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/lib/sentinelHub.ts:204
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/mesh/infonetEconomyClient.ts:17
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/mesh/meshDmClient.ts:355
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/mesh/privacyCoreWasm/privacy_core.js:421
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph hardware Supply chain conf 1.00 Dockerfile ADD downloads remote content without checksum
Remote build inputs can change or be replaced upstream. Use Dockerfile ADD --checksum or download with an explicit digest/signature verification step.
backend/Dockerfile:37 containersChecksum
medium System graph cicd CI/CD security conf 1.00 9 occurrences GitHub Action is tag-pinned rather than SHA-pinned
astral-sh/setup-uv@v5 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 9 locations
.github/workflows/docker-publish.yml:41, 47, 51, 96, 132, 138, 142, 188 (8 hits)
.github/workflows/ci.yml:61
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/docker-publish.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in backend/main.py:8484
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
backend/main.py:8484 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in backend/routers/cctv.py:222
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
backend/routers/cctv.py:222 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in desktop-shell/scripts/run-desktop-build.cjs:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
desktop-shell/scripts/run-desktop-build.cjs:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in desktop-shell/tauri-skeleton/scripts/build-backend-runtime.cjs:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
desktop-shell/tauri-skeleton/scripts/build-backend-runtime.cjs:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in desktop-shell/tauri-skeleton/scripts/build-frontend-export.cjs:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
desktop-shell/tauri-skeleton/scripts/build-frontend-export.cjs:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in frontend/scripts/build-privacy-core-wasm.cjs:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
frontend/scripts/build-privacy-core-wasm.cjs:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in frontend/scripts/dev-all.cjs:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
frontend/scripts/dev-all.cjs:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in frontend/scripts/vite-no-net-use.cjs:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
frontend/scripts/vite-no-net-use.cjs:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/mesh/smoke-dm-root-deployment-flow.mjs:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/mesh/smoke-dm-root-deployment-flow.mjs:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/mesh/smoke-external-root-witness-flow.mjs:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/mesh/smoke-external-root-witness-flow.mjs:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/mesh/sync-dm-root-external-assurance.mjs:5
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/mesh/sync-dm-root-external-assurance.mjs:5 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in start-backend.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
start-backend.js:1 Node child process
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — backend/services/ais_stream.py:620
`subprocess.Popen(...)` 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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — backend/services/infonet/governance/dsl_executor.py:198
`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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — backend/services/mesh/mesh_wormhole_prekey.py:235
`requests.get(...)` 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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — backend/services/updater.py:504
`subprocess.Popen(...)` 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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/e2e_dm_short_address_live.py:184
`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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/sanitize_submarine_cables.py:105
`urllib.request.urlretrieve(...)` 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 quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 152 placeholder/mock markers across 50 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration
A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.
Runtime configService clientGenerated repo pattern
low System graph quality Integrity conf 1.00 200 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `AGENT_SHELL_DEFAULT_CWD`, `AISHUB_POLL_INTERVAL_MINUTES`, `AISHUB_USERNAME`, `ALERTS_IN_UA_TOKEN`, `BACKEND_BASE_PYTHON`, `BACKEND_PORT`, `BACKEND_RELOAD`, `BACKEND_URL` + 192 more. Add them (with a placeholder/comment) to .env.example so onboardi…
config drift
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 322 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: node:20-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
frontend/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.11-slim-bookworm
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
backend/Dockerfile:21 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: rust:1.88-slim-bookworm
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
backend/Dockerfile:2 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
actions/setup-python@v5 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/ci.yml:65 CI/CD securitySupply chainGithub actions
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/src/components/KeyboardShortcutsOverlay.tsx:53
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/src/components/MaplibreViewer/popups/MilitaryBasePopup.tsx:79
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/src/components/MaplibreViewer/popups/ShipPopup.tsx:50
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — frontend/src/components/MaplibreViewer/popups/SigintPopup.tsx:126
A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label
Fq button no label
low System graph quality Integrity conf 1.00 19 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/main.py:oracle_region_intel, backend/routers/sigint.py:oracle_region_intel This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
19 occurrences
repo-level (19 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: backend/main.py:infonet_sync_post, backend/main.py:infonet_sync, backend/routers/mesh_public.py:infonet_sync_post, backend/routers/mesh_public.py:infonet_sync This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://…
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `__test_legacy` in backend/tests/mesh/test_s13c_gate_envelope_policy.py:124
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 quality Integrity conf 1.00 Old/deprecated-named symbol `__test_s13d_legacy` in backend/tests/mesh/test_s13d_legacy_envelope_fallback.py:73
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 quality Integrity conf 1.00 Old/deprecated-named symbol `_derive_seal_key_v2` in backend/services/mesh/mesh_wormhole_seal.py:54
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 quality Integrity conf 1.00 Old/deprecated-named symbol `_extract_and_copy` in backend/tests/test_gdelt_updater_hardening.py:67
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 quality Integrity conf 1.00 Old/deprecated-named symbol `_get_security_posture_warnings_legacy` in backend/services/env_check.py:650
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 quality Integrity conf 1.00 Old/deprecated-named symbol `allow_legacy` in backend/services/mesh/mesh_wormhole_persona.py:846
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 quality Integrity conf 1.00 Old/deprecated-named symbol `cameras_v1` in backend/services/cctv_pipeline.py:797
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 quality Integrity conf 1.00 Old/deprecated-named symbol `collect_legacy` in backend/main.py:7853
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 quality Integrity conf 1.00 Old/deprecated-named symbol `collect_legacy` in backend/services/mesh/mesh_dm_relay.py:2066
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 quality Integrity conf 1.00 Old/deprecated-named symbol `collect_legacy` in backend/tests/mesh/test_dm_poll_batch_limit.py:121
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 quality Integrity conf 1.00 Old/deprecated-named symbol `compressed_v1` in backend/routers/ai_intel.py:767
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 quality Integrity conf 1.00 Old/deprecated-named symbol `compressed_v1` in backend/services/openclaw_channel.py:565
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 quality Integrity conf 1.00 Old/deprecated-named symbol `count_legacy` in backend/tests/mesh/test_compatibility_containment.py:206
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 quality Integrity conf 1.00 Old/deprecated-named symbol `count_legacy` in backend/tests/mesh/test_mesh_dm_security.py:106
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 quality Integrity conf 1.00 Old/deprecated-named symbol `count_legacy` in backend/tests/mesh/test_private_metadata_exposure.py:407
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 quality Integrity conf 1.00 Old/deprecated-named symbol `count_legacy` in backend/tests/mesh/test_s16a_dm_count_coarsening.py:181
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 quality Integrity conf 1.00 Old/deprecated-named symbol `dirs_to_backup` in backend/services/updater.py:393
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 quality Integrity conf 1.00 Old/deprecated-named symbol `dm_test_legacy` in backend/tests/mesh/test_mesh_wormhole_hardening.py:747
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 quality Integrity conf 1.00 Old/deprecated-named symbol `event_copy` in backend/services/fetchers/geo.py:269
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 quality Integrity conf 1.00 Old/deprecated-named symbol `from_buffer_copy` in backend/services/privacy_core_client.py:576
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 quality Integrity conf 1.00 Old/deprecated-named symbol `kiwisdr_consent_v1` in frontend/src/components/WorldviewLeftPanel.tsx:481
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 quality Integrity conf 1.00 Old/deprecated-named symbol `m_old` in backend/services/infonet/tests/test_5_dispute_bounded_reversal.py:218
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 quality Integrity conf 1.00 Old/deprecated-named symbol `m_old` in backend/services/infonet/tests/test_8_eligibility.py:105
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 quality Integrity conf 1.00 Old/deprecated-named symbol `mls_v1` in backend/tests/mesh/test_s13b_gate_identity_surface.py:49
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 quality Integrity conf 1.00 Old/deprecated-named symbol `normalize_dm_message_payload_legacy` in backend/services/mesh/mesh_protocol.py:272
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 quality Integrity conf 1.00 Old/deprecated-named symbol `normalize_dm_message_payload_legacy` in backend/services/mesh/mesh_signed_events.py:31
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 quality Integrity conf 1.00 Old/deprecated-named symbol `normalize_dm_message_payload_legacy` in backend/tests/mesh/test_mesh_rns_private_dm.py:24
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 quality Integrity conf 1.00 Old/deprecated-named symbol `peer_sender_legacy` in backend/tests/mesh/test_dm_alias_rotation_binding.py:560
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 quality Integrity conf 1.00 Old/deprecated-named symbol `preds_copy` in backend/services/road_corridor_sat/s2_truck_detect.py:484
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 quality Integrity conf 1.00 Old/deprecated-named symbol `rest_v1` in backend/services/region_dossier.py:177
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 quality Integrity conf 1.00 Old/deprecated-named symbol `rust_backup` in backend/tests/mesh/test_gate_state_resync.py:171
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 quality Integrity conf 1.00 Old/deprecated-named symbol `sb_dm_alias_payload_v1` in backend/services/mesh/mesh_wormhole_dead_drop.py:89
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 quality Integrity conf 1.00 Old/deprecated-named symbol `sb_gate_compat_approvals_v2` in frontend/src/mesh/wormholeIdentityClient.ts:42
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 quality Integrity conf 1.00 Old/deprecated-named symbol `sb_gate_compat_telemetry_v1` in frontend/src/mesh/gateCompatTelemetry.ts:4
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 quality Integrity conf 1.00 Old/deprecated-named symbol `sb_infonet_mailbox_v1` in frontend/src/__tests__/mesh/messagesViewFirstContact.test.tsx:488
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 quality Integrity conf 1.00 Old/deprecated-named symbol `sb_infonet_mailbox_v1` in frontend/src/components/InfonetTerminal/MessagesView.tsx:208
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 quality Integrity conf 1.00 Old/deprecated-named symbol `sb_legacy` in frontend/src/__tests__/mesh/meshDmClientLookup.test.ts:18
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 quality Integrity conf 1.00 Old/deprecated-named symbol `sb_legacy` in frontend/src/__tests__/mesh/meshGateWorkerVault.test.ts:199
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 quality Integrity conf 1.00 Old/deprecated-named symbol `sb_old` in backend/tests/mesh/test_signed_write_transport_matrix.py:215
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 quality Integrity conf 1.00 Old/deprecated-named symbol `sb_shodan_presets_v1` in frontend/src/components/ShodanPanel.tsx:44
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 quality Integrity conf 1.00 Old/deprecated-named symbol `sb_unused` in backend/tests/mesh/test_mesh_gate_mls.py:132
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 quality Integrity conf 1.00 Old/deprecated-named symbol `sb_v1` in backend/tests/mesh/test_mesh_reputation_link.py:33
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 quality Integrity conf 1.00 Old/deprecated-named symbol `spk_too_old` in backend/services/mesh/mesh_wormhole_prekey.py:1103
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 quality Integrity conf 1.00 Old/deprecated-named symbol `store_backup` in backend/services/mesh/mesh_gate_mls.py:998
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 quality Integrity conf 1.00 Old/deprecated-named symbol `test_economy_types_disjoint_from_legacy_legacy` in backend/services/infonet/tests/test_1_schema_event_types.py:30
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 quality Integrity conf 1.00 Old/deprecated-named symbol `test_public_ledger_is_union_of_active_and_legacy` in backend/tests/mesh/test_ledger_policy_split.py:37
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 quality Integrity conf 1.00 Old/deprecated-named symbol `v1_upreps_v2` in backend/services/infonet/reputation/anti_gaming/clustering.py:98
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: clear_injected_data
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/ai_intel_store.py:160
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_generate_keypair
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scripts/bootstrap_manifest_helper.py:48
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_hash
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scripts/release_helper.py:146
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_set_version
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scripts/release_helper.py:138
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_show
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scripts/release_helper.py:127
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_sign
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scripts/bootstrap_manifest_helper.py:54
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_write_attestation
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scripts/release_helper.py:178
low System graph software Dead code conf 1.00 Possibly dead Python function: fetch_darkpool_recent
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/unusual_whales_connector.py:304
low System graph software Dead code conf 1.00 Possibly dead Python function: infrastructure_to_stix
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/stix_exporter.py:80
low System graph software Dead code conf 1.00 Possibly dead Python function: malware_to_stix
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/stix_exporter.py:60
low System graph software Dead code conf 1.00 Possibly dead Python function: run_all_ingestors
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/cctv_pipeline.py:1439
low System graph software Dead code conf 1.00 Possibly dead Python function: schedule_restart
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/updater.py:489
low System graph software Dead code conf 1.00 Possibly dead Python function: send_contact_accept
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/openclaw_infonet.py:647
low System graph software Dead code conf 1.00 Possibly dead Python function: setup_logging
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/logging_setup.py:22
low System graph software Dead code conf 1.00 Possibly dead Python function: start_cover_poll
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/openclaw_channel.py:1750
low System graph software Dead code conf 1.00 Possibly dead Python function: stop_cover_poll
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/openclaw_channel.py:1763
low System graph software Dead code conf 1.00 Possibly dead Python function: stop_feed_ingester
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/feed_ingester.py:242
low System graph software Dead code conf 1.00 Possibly dead Python function: stop_watchdog
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/openclaw_watchdog.py:525
low System graph software Dead code conf 1.00 Possibly dead Python function: threat_actor_to_stix
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/stix_exporter.py:37
low System graph software Dead code conf 1.00 Possibly dead Python function: update_ais_bbox
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/ais_stream.py:843
low System graph software Dead code conf 1.00 Possibly dead Python function: validate_geocode
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/geocode_validate.py:233
low System graph software Dead code conf 1.00 Possibly dead Python function: vulnerability_to_stix
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/stix_exporter.py:98
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — backend/ais_proxy.js:240
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — frontend/scripts/report-bundle-size.js:24
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — frontend/src/components/RadioInterceptPanel.tsx:181
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — start-backend.js:112
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph quality Integrity conf 1.00 Stub function `_noop_progress` (body is just `pass`/`return`) — backend/services/road_corridor_sat/pipeline.py:29
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph quality Integrity conf 1.00 Stub function `fetch_data` (body is just `pass`/`return`) — backend/services/cctv_pipeline.py:298
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/mesh/peers
`backend/main.py` declares `DELETE /api/mesh/peers` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/mesh/channels
`backend/main.py` declares `GET /api/mesh/channels` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/mesh/gate/list
`backend/main.py` declares `GET /api/mesh/gate/list` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/mesh/gate/{gate_id}
`backend/main.py` declares `GET /api/mesh/gate/{gate_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/mesh/gate/{gate_id}/messages
`backend/main.py` declares `GET /api/mesh/gate/{gate_id}/messages` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/mesh/infonet/bootstrap-manifest
`backend/main.py` declares `GET /api/mesh/infonet/bootstrap-manifest` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/mesh/infonet/event/{event_id}
`backend/main.py` declares `GET /api/mesh/infonet/event/{event_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/mesh/infonet/locator
`backend/main.py` declares `GET /api/mesh/infonet/locator` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/mesh/infonet/merkle
`backend/main.py` declares `GET /api/mesh/infonet/merkle` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/mesh/infonet/messages
`backend/main.py` declares `GET /api/mesh/infonet/messages` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/mesh/infonet/messages/wait
`backend/main.py` declares `GET /api/mesh/infonet/messages/wait` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/mesh/infonet/peer-registry
`backend/main.py` declares `GET /api/mesh/infonet/peer-registry` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/mesh/infonet/status
`backend/main.py` declares `GET /api/mesh/infonet/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/mesh/infonet/sync
`backend/main.py` declares `GET /api/mesh/infonet/sync` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/mesh/log
`backend/main.py` declares `GET /api/mesh/log` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/mesh/messages
`backend/main.py` declares `GET /api/mesh/messages` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/mesh/metrics
`backend/main.py` declares `GET /api/mesh/metrics` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/mesh/peers
`backend/main.py` declares `GET /api/mesh/peers` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/mesh/reputation
`backend/main.py` declares `GET /api/mesh/reputation` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/mesh/reputation/all
`backend/main.py` declares `GET /api/mesh/reputation/all` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/mesh/reputation/batch
`backend/main.py` declares `GET /api/mesh/reputation/batch` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/mesh/rns/status
`backend/main.py` declares `GET /api/mesh/rns/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/mesh/signals
`backend/main.py` declares `GET /api/mesh/signals` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/mesh/status
`backend/main.py` declares `GET /api/mesh/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/oracle/region-intel
`backend/main.py` declares `GET /api/oracle/region-intel` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/privacy/claims
`backend/main.py` declares `GET /api/privacy/claims` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/refresh
`backend/main.py` declares `GET /api/refresh` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/sigint/nearest-sdr
`backend/main.py` declares `GET /api/sigint/nearest-sdr` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/thermal/verify
`backend/main.py` declares `GET /api/thermal/verify` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/mesh/peers
`backend/main.py` declares `PATCH /api/mesh/peers` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/ais/feed
`backend/main.py` declares `POST /api/ais/feed` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/layers
`backend/main.py` declares `POST /api/layers` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/mesh/gate/create
`backend/main.py` declares `POST /api/mesh/gate/create` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/mesh/gate/peer-pull
`backend/main.py` declares `POST /api/mesh/gate/peer-pull` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/mesh/gate/peer-push
`backend/main.py` declares `POST /api/mesh/gate/peer-push` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/mesh/gate/{gate_id}/message
`backend/main.py` declares `POST /api/mesh/gate/{gate_id}/message` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/mesh/identity/revoke
`backend/main.py` declares `POST /api/mesh/identity/revoke` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/mesh/identity/rotate
`backend/main.py` declares `POST /api/mesh/identity/rotate` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/mesh/infonet/ingest
`backend/main.py` declares `POST /api/mesh/infonet/ingest` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/mesh/infonet/peer-announce
`backend/main.py` declares `POST /api/mesh/infonet/peer-announce` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/mesh/infonet/peer-push
`backend/main.py` declares `POST /api/mesh/infonet/peer-push` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/mesh/infonet/sync
`backend/main.py` declares `POST /api/mesh/infonet/sync` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/mesh/peers
`backend/main.py` declares `POST /api/mesh/peers` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/mesh/report
`backend/main.py` declares `POST /api/mesh/report` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/mesh/send
`backend/main.py` declares `POST /api/mesh/send` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/mesh/vote
`backend/main.py` declares `POST /api/mesh/vote` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/sigint/transmit
`backend/main.py` declares `POST /api/sigint/transmit` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/viewport
`backend/main.py` declares `POST /api/viewport` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /api/mesh/gate/{gate_id}/envelope_policy
`backend/main.py` declares `PUT /api/mesh/gate/{gate_id}/envelope_policy` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /api/mesh/gate/{gate_id}/legacy_envelope_fallback
`backend/main.py` declares `PUT /api/mesh/gate/{gate_id}/legacy_envelope_fallback` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: backend/auth.py (1508 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/main.py (12120 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/routers/ai_intel.py (3491 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/routers/mesh_public.py (2363 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/routers/wormhole.py (1501 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/services/cctv_pipeline.py (1460 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/services/env_check.py (1159 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/services/fetchers/earth_observation.py (1790 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/services/fetchers/satellites.py (1057 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/services/mesh/mesh_dm_relay.py (2140 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/services/mesh/mesh_gate_mls.py (2443 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/services/mesh/mesh_hashchain.py (3340 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/services/mesh/mesh_reputation.py (1572 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/services/mesh/mesh_rns.py (1986 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/services/mesh/mesh_router.py (1343 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/services/mesh/mesh_signed_events.py (1466 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/services/mesh/mesh_wormhole_contacts.py (1878 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/services/mesh/mesh_wormhole_dead_drop.py (1303 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/services/mesh/mesh_wormhole_identity.py (1843 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/services/mesh/mesh_wormhole_persona.py (1509 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/services/mesh/mesh_wormhole_prekey.py (1584 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/services/mesh/mesh_wormhole_root_manifest.py (2174 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/services/openclaw_channel.py (1773 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/services/privacy_claims.py (1769 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/services/sigint_bridge.py (1459 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/services/telemetry.py (2428 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/tests/mesh/test_mesh_endpoint_integrity.py (3369 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/tests/mesh/test_mesh_privacy_hardening.py (1536 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/tests/mesh/test_mesh_rns_private_dm.py (1480 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/tests/mesh/test_privacy_claims.py (2378 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: backend/tests/mesh/test_s16d_dm_invite_bootstrap.py (1421 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/components/AIIntelPanel.tsx (1945 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/components/InfonetTerminal/MessagesView.tsx (3889 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/components/map/geoJSONBuilders.ts (1958 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/components/MaplibreViewer.tsx (6535 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/components/MeshChat/index.tsx (1757 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/components/MeshChat/useMeshChatController.ts (4836 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/components/MeshTerminal.tsx (6139 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/components/NewsFeed.tsx (2022 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/components/PredictionsPanel.tsx (1196 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/components/SettingsPanel.tsx (3117 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/components/TopRightControls.tsx (1270 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/components/WorldviewLeftPanel.tsx (2088 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/mesh/meshIdentity.ts (1824 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/src/mesh/wormholeIdentityClient.ts (2200 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: openclaw-skills/shadowbroker/sb_query.py (1403 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: privacy-core/src/lib.rs (2254 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: scripts/e2e_dm_short_address_live.py (3579 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/2cab8c28-e7ac-4a2d-8a5f-676860f6a72a/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/2cab8c28-e7ac-4a2d-8a5f-676860f6a72a/

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.