high System graph api Wiring conf 1.00 Dangling fetch: GET /api/v1/stats/exchange-rates (frontend/src/lib/exchangeRates.ts:26)

`frontend/src/lib/exchangeRates.ts:26` calls `GET /api/v1/stats/exchange-rates` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/stats/exchange-rates` If this points at an external API, prefix it with `https://` so…

Dangling fetchFetch

high System graph security auth conf 1.00 FastAPI POST `submit_issue` without auth dependency — backend/api/routers/issues.py:80

`@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/api/routers/issues.py:80 securityAuth fastapi unauth mutation

high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in backend/scripts/archive/load_asf_mdb.py:64

Found a known-risky pattern (tls_verify_false). Review and replace if possible.

backend/scripts/archive/load_asf_mdb.py:64 Tls verify false

high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in backend/scripts/enrich_vendor_names_qqw.py:115

Found a known-risky pattern (tls_verify_false). Review and replace if possible.

backend/scripts/enrich_vendor_names_qqw.py:115 Tls verify false

high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in backend/scripts/load_sat_efos.py:102

Found a known-risky pattern (tls_verify_false). Review and replace if possible.

backend/scripts/load_sat_efos.py:102 Tls verify false

medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/pages/PriceIntelligence.tsx:1713

Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html

Fq dangerous html

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/hooks/useWikipediaImage.ts:22

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 Agent instructions conf 1.00 Agent authority lacks a verifier contract: frontend/.mcp.json

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

frontend/.mcp.json VerificationMcp config

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 Security conf 1.00 Dockerfile runs as root: frontend/Dockerfile

No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.

Container

medium System graph quality Integrity conf 1.00 104 occurrences Frontend route `login` has no Link/navigate to it — frontend/src/App.tsx

The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.

104 occurrences

repo-level (104 hits)

Orphan pageWiring

medium System graph cicd CI/CD security conf 1.00 9 occurrences GitHub Action is tag-pinned rather than SHA-pinned

codecov/codecov-action@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

6 files, 9 locations

.github/workflows/codeql.yml:29, 35, 38 (3 hits)

.github/workflows/deploy.yml:15, 43 (2 hits)

.github/workflows/backend-tests.yml:47

.github/workflows/bundle-size.yml:24

.github/workflows/frontend-tests.yml:49

.github/workflows/lighthouse.yml:35

CI/CD securitySupply chainGithub actions

medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/pages/PriceIntelligence.tsx:1713

Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.

frontend/src/pages/PriceIntelligence.tsx:1713 Dangerous innerhtml

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/components/InstitutionBadge.tsx:62

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

frontend/src/components/InstitutionBadge.tsx:62 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in frontend/scripts/lint-tokens.mjs:20

Found a known-risky pattern (node_child_process). Review and replace if possible.

frontend/scripts/lint-tokens.mjs:20 Node child process

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — backend/scripts/_build_deploy_db.py:179

`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/scripts/add_efos_ground_truth.py:162

`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/scripts/timing_test.py:46

`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 Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 103 placeholder/mock markers across 56 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 network Security conf 1.00 Privileged port 30 in use

Port 30 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.

backend/scripts/backup_db.sh Ports

medium System graph quality Tests conf 1.00 Very low test-to-source ratio

58 test file(s) for 1103 source file(s) (ratio 0.05). Consider adding integration or unit tests for critical paths.

Coverage

low System graph quality Integrity conf 1.00 23 env vars used in code but missing from .env.example

Drift between code and config docs. The first few: `ANTHROPIC_API_KEY`, `ARIA_TIER1_THRESHOLD`, `ARIA_TIER2_THRESHOLD`, `ARIA_TIER3_THRESHOLD`, `ARIA_W_ENSEMBLE`, `ARIA_W_EXTERNAL`, `ARIA_W_FINANCIAL`, `ARIA_W_RISK` + 15 more. Add them (with a placeholder/comment) to .env.example so onboarding does…

config drift

low System graph quality Maintenance conf 1.00 53 TODO/FIXME markers

High count of TODO/FIXME/HACK markers — track them as issues so they're not forgotten.

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 7202 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: nginx: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:20 containersPinned dependencies

low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:22-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:3 containersPinned dependencies

low System graph hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: python:3.11-slim

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

lines 3, 21

backend/Dockerfile:3, 21 (2 hits)

containersPinned dependencies

low System graph software Dead code candidate conf 1.00 File has no detected symbols: backend/scripts/_tmp_scan.py

Source file with no class/function declarations — possible config, dead code, or scratch file.

low System graph software Dead code candidate conf 1.00 File has no detected symbols: backend/scripts/_tmp_scan2.py

Source file with no class/function declarations — possible config, dead code, or scratch file.

low System graph cicd CI/CD security conf 1.00 4 occurrences 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.

2 files, 4 locations

.github/workflows/backend-tests.yml:22, 60 (2 hits)

.github/workflows/frontend-tests.yml:22, 62 (2 hits)

CI/CD securitySupply chainGithub actions

low System graph security security conf 1.00 Insecure pattern 'document_write' in frontend/src/components/ReportModal.tsx:178

Found a known-risky pattern (document_write). Review and replace if possible.

frontend/src/components/ReportModal.tsx:178 Document write

low System graph quality Integrity conf 1.00 16 occurrences Near-duplicate function bodies in 2 places

Functions with the same first-5-line body hash: scripts/automated_explore.py:main_async, scripts/automated_explore.py:main 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.

16 occurrences

repo-level (16 hits)

duplicatesduplication

low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 3 places

Functions with the same first-5-line body hash: backend/api/cache.py:get_cache, backend/api/cache.py:get, backend/api/cache.py:get 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.

2 occurrences

repo-level (2 hits)

duplicatesduplication

low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 38 places

Functions with the same first-5-line body hash: backend/scripts/_aria_cases_439_440.py:run, backend/scripts/_aria_cases_443_445.py:run, backend/scripts/_aria_cases_586_589.py:run, backend/scripts/_aria_cases_581_585.py:run This is *the* AI-coder failure mode (4× more duplication in vibe-coded repo…

duplicatesduplication

low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 5 places

Functions with the same first-5-line body hash: backend/scripts/_aria_cases_batch_BBB.py:main, backend/scripts/_aria_cases_batch_Z.py:main, backend/scripts/_aria_cases_batch_BB.py:main, backend/scripts/_aria_cases_batch_W.py:main This is *the* AI-coder failure mode (4× more duplication in vibe-cod…

duplicatesduplication

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_get_last_backup` in backend/api/routers/health.py:114

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 `capture_landscape_v1` in backend/api/routers/capture.py:346

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 `cluster_vendors_v2` in backend/scripts/archive/cluster_vendors_v2.py: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 `compute_score_old` in backend/scripts/_calibration_estimate.py:6

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 `days_old` in backend/scripts/aria_investigate.py:93

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 `days_old` in backend/scripts/centinela.py:134

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 `decentralized_legacy` in backend/scripts/classify_institutions.py:101

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 `decentralized_legacy` in backend/scripts/etl_create_schema.py:1018

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 `ExploreLegacy` in frontend/src/App.tsx:34

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 `ips_old` in backend/scripts/recompute_ips_with_novelty.py:53

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 `match_corporate_groups_v2` in backend/scripts/match_corporate_groups_v2.py:12

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 `model_copy` in backend/api/routers/institutions.py:1565

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 `network_trama_index_v1` in backend/api/routers/network.py:814

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 `network_trama_index_v1` in backend/scripts/_precompute_network_trama.py:7

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 `old_backup` in backend/scripts/backup_database.py:71

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 `r_old` in backend/tests/test_subnational.py:61

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 `rate_v1` in backend/scripts/analyze_co_bidding.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 `rate_v1` in backend/scripts/archive/calculate_risk_scores.py:465

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 `rate_v1` in backend/scripts/explore_detectable_patterns.py:125

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 frontend/src/hooks/useWikipediaImage.ts:7

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 `rubli_atlas_saved_view_v1` in frontend/src/components/atlas/AtlasLeftRail.tsx:141

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 `rubli_atlas_visited_v1` in frontend/src/pages/Atlas.tsx:5

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 `rubli_explore_pin_v1` in frontend/src/components/explore/ExploreState.tsx:50

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 `rubli_explore_recent_v1` in frontend/src/components/explore/SearchOverlay.tsx:29

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 `rubli_explore_recent_v1` in frontend/src/pages/VendorProfile.tsx:178

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 `rubli_explore_visited_v1` in frontend/src/pages/SpatialMap.tsx: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 `rubli_trama_pins_v1` in frontend/src/pages/RedesKnownDossier.tsx:45

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 `RUBLI_v1` in backend/api/routers/cases.py:101

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 `RUBLI_v1` in backend/api/routers/categories.py:223

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 `rubli_wayfinding_scroll_v1` in frontend/src/hooks/useWayfindingScroll.ts:29

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 `run_backup` in backend/scripts/backup_db.py:80

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 `sectors_treemap_v1` in backend/api/routers/sectors.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 `template_v1` in backend/scripts/_write_memos_307_309.py:255

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: behavior_click_random

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

scripts/automated_explore.py:285

low System graph software Dead code conf 1.00 Possibly dead Python function: behavior_hover

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

scripts/automated_explore.py:318

low System graph software Dead code conf 1.00 Possibly dead Python function: behavior_press_key

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

scripts/automated_explore.py:333

low System graph software Dead code conf 1.00 Possibly dead Python function: behavior_scroll

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

scripts/automated_explore.py:301

low System graph software Dead code conf 1.00 Possibly dead Python function: behavior_type_search

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

scripts/automated_explore.py:342

low System graph software Dead code conf 1.00 Possibly dead Python function: compute_binary_stats

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/scripts/compute_factor_baselines.py:79

low System graph software Dead code conf 1.00 Possibly dead Python function: compute_continuous_stats

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/scripts/compute_factor_baselines.py:90

low System graph software Dead code conf 1.00 Possibly dead Python function: get_importance_plot_base64

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/scripts/investigation_shap_visualizations.py:532

low System graph software Dead code conf 1.00 Possibly dead Python function: get_summary_plot_base64

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/scripts/investigation_shap_visualizations.py:527

low System graph software Dead code conf 1.00 Possibly dead Python function: noop_decorator

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/api/routers/sectors.py:42

low System graph software Dead code conf 1.00 Possibly dead Python function: objective

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/scripts/calibrate_risk_model_v5.py:305

low System graph software Dead code conf 1.00 Possibly dead Python function: refresh_asf

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/scripts/centinela.py:358

low System graph software Dead code conf 1.00 Possibly dead Python function: refresh_efos

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/scripts/centinela.py:174

low System graph software Dead code conf 1.00 Possibly dead Python function: refresh_rfc

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/scripts/centinela.py:527

low System graph software Dead code conf 1.00 Possibly dead Python function: refresh_rupc

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/scripts/centinela.py:255

low System graph software Dead code conf 1.00 Possibly dead Python function: refresh_sfp

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

backend/scripts/centinela.py:209

low System graph frontend Frontend quality conf 1.00 React Flow edge with `label=` but no project-wide edge-label CSS override — frontend/src/components/charts/TemporalRiskChart.tsx:325

React Flow edge labels render with a white rectangle behind the text by default, which scatters bright boxes across a dark canvas. Either drop the label, or override `.react-flow__edge-textbg` and `.react-flow__edge-text` in your stylesheet. Why: P-H in CHECKLIST.md — vendor edge labels bleed whit…

Fq edge label no bg

low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence

The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.

Git historyGenerated repo pattern

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/run_visual_review.js:25

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 api Wiring conf 1.00 Unused endpoint: DELETE /

`backend/api/routers/feedback.py` declares `DELETE /` 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: DELETE /{folder_id}

`backend/api/routers/watchlist_folders.py` declares `DELETE /{folder_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 /

`backend/api/main.py` declares `GET /` 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 /administration-comparison

`backend/api/routers/stories.py` declares `GET /administration-comparison` 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 /capture-leaders

`backend/api/routers/executive.py` declares `GET /capture-leaders` 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 /co-bidders/{vendor_id}

`backend/api/routers/network.py` declares `GET /co-bidders/{vendor_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 /communities

`backend/api/routers/network.py` declares `GET /communities` 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 /communities/index

`backend/api/routers/network.py` declares `GET /communities/index` 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 /communities/{community_id}

`backend/api/routers/network.py` declares `GET /communities/{community_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 /communities/{community_id}/graph

`backend/api/routers/network.py` declares `GET /communities/{community_id}/graph` 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 api Wiring conf 1.00 Unused endpoint: GET /dashboard-bundle

`backend/api/routers/executive.py` declares `GET /dashboard-bundle` 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 /export/{folder_id}

`backend/api/routers/watchlist_folders.py` declares `GET /export/{folder_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 /flash-vendors

`backend/api/routers/analysis_vendor_sector.py` declares `GET /flash-vendors` 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 /ghost-companies

`backend/api/routers/stories.py` declares `GET /ghost-companies` 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 /graph

`backend/api/routers/network.py` declares `GET /graph` 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 /industry-risk-clusters

`backend/api/routers/analysis_vendor_sector.py` declares `GET /industry-risk-clusters` 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 cons…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /institution-capture

`backend/api/routers/network.py` declares `GET /institution-capture` 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 /institution-capture/{institution_id}/star

`backend/api/routers/network.py` declares `GET /institution-capture/{institution_id}/star` 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 …

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /institution-risk-factors

`backend/api/routers/analysis_vendor_sector.py` declares `GET /institution-risk-factors` 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 co…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /institution-vendors/{institution_id}

`backend/api/routers/network.py` declares `GET /institution-vendors/{institution_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 consu…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /institution/{institution_id}

`backend/api/routers/reports.py` declares `GET /institution/{institution_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 /institution/{institution_id}/period-comparison

`backend/api/routers/analysis_patterns.py` declares `GET /institution/{institution_id}/period-comparison` 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 d…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /institutions

`backend/api/routers/scorecards.py` declares `GET /institutions` 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 /institutions/stats

`backend/api/routers/scorecards.py` declares `GET /institutions/stats` 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 /institutions/{institution_id}

`backend/api/routers/scorecards.py` declares `GET /institutions/{institution_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 …

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /leads

`backend/api/routers/analysis_patterns.py` declares `GET /leads` 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 /monthly-risk-summary

`backend/api/routers/analysis_vendor_sector.py` declares `GET /monthly-risk-summary` 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 consum…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /movers

`backend/api/routers/officials.py` declares `GET /movers` 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 /overpricing-patterns

`backend/api/routers/stories.py` declares `GET /overpricing-patterns` 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 /pattern-spotlight

`backend/api/routers/network.py` declares `GET /pattern-spotlight` 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 /patterns/co-bidding

`backend/api/routers/analysis_patterns.py` declares `GET /patterns/co-bidding` 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 /patterns/concentration

`backend/api/routers/analysis_patterns.py` declares `GET /patterns/concentration` 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 api Wiring conf 1.00 Unused endpoint: GET /patterns/year-end

`backend/api/routers/analysis_patterns.py` declares `GET /patterns/year-end` 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 /procedure-risk-comparison

`backend/api/routers/analysis_vendor_sector.py` declares `GET /procedure-risk-comparison` 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 c…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /related-vendors/{vendor_id}

`backend/api/routers/network.py` declares `GET /related-vendors/{vendor_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 /seasonal-risk

`backend/api/routers/analysis_vendor_sector.py` declares `GET /seasonal-risk` 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 /sector-growth

`backend/api/routers/analysis_vendor_sector.py` declares `GET /sector-growth` 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 /sector/{sector_id}

`backend/api/routers/reports.py` declares `GET /sector/{sector_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 /summary

`backend/api/routers/executive.py` declares `GET /summary` 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 /thematic/{theme}

`backend/api/routers/reports.py` declares `GET /thematic/{theme}` 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 /top-by-period

`backend/api/routers/analysis_vendor_sector.py` declares `GET /top-by-period` 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 /top-suspicious-vendors

`backend/api/routers/stories.py` declares `GET /top-suspicious-vendors` 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 /value-concentration

`backend/api/routers/analysis_vendor_sector.py` declares `GET /value-concentration` 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 consume…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /vendor/{vendor_id}

`backend/api/routers/reports.py` declares `GET /vendor/{vendor_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 /vendors

`backend/api/routers/scorecards.py` declares `GET /vendors` 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 /vendors/{vendor_id}

`backend/api/routers/scorecards.py` declares `GET /vendors/{vendor_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 /year-summary/{year}

`backend/api/routers/analysis_vendor_sector.py` declares `GET /year-summary/{year}` 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 consume…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /{name}

`backend/api/routers/officials.py` declares `GET /{name}` 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 /

`backend/api/routers/watchlist_folders.py` declares `POST /` 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 /{folder_id}

`backend/api/routers/watchlist_folders.py` declares `PUT /{folder_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 quality Complexity conf 1.00 Very large file: backend/api/routers/analysis.py (4999 lines)