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

dare2live/lifehack

https://github.com/dare2live/lifehack · scanned 2026-06-17 01:53 UTC (1 month, 1 week ago)

193 raw signals (0 security + 193 graph)

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

Complete repo analysis

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

JSON
Combined
73.0
/100
Security checks
73
0 findings
System graph
73
88.9% cov · 175 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 33 Medium 30 Low 96 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 175 Crowd 0 Layer: Software 18 Security 32 Cicd 1 Quality 67 Api 57
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 73.0/100 with 88.9% coverage. It contains 7910 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 193 findings — concentrated in quality (84), api (57), security (32). Risk profile is high: 0 critical, 33 high, 30 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 159 of 175 actionable findings. 193 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.

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/config/decision_views (frontend/js/modules/decision_views.js:143)
`frontend/js/modules/decision_views.js:143` calls `GET /api/config/decision_views` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/config/decision_views` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/config/report_template (frontend/js/screens_reportpage.js:177)
`frontend/js/screens_reportpage.js:177` calls `GET /api/config/report_template` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/config/report_template` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/industry/overview (frontend/js/screens_reportpage.js:181)
`frontend/js/screens_reportpage.js:181` calls `GET /api/industry/overview` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/industry/overview` If this points at an external API, prefix it with `https://` so the matche…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/industry/overview (frontend/js/screens_tools.js:510)
`frontend/js/screens_tools.js:510` calls `GET /api/industry/overview` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/industry/overview` If this points at an external API, prefix it with `https://` so the matcher ski…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/tools/workflow/task-claims/${encodeURIComponent(claimId)} (frontend/js/screens_tool_registry.js:680)
`frontend/js/screens_tool_registry.js:680` calls `PATCH /api/tools/workflow/task-claims/${encodeURIComponent(claimId)}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/tools/workflow/task-claims/<p>` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/tools/workflow/task-claims (frontend/js/screens_tool_registry.js:646)
`frontend/js/screens_tool_registry.js:646` calls `POST /api/tools/workflow/task-claims` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/tools/workflow/task-claims` If this points at an external API, prefix it with `h…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/tools/workflow/task-results (frontend/js/screens_tool_registry.js:719)
`frontend/js/screens_tool_registry.js:719` calls `POST /api/tools/workflow/task-results` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/tools/workflow/task-results` If this points at an external API, prefix it with …
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI DELETE `clear_answers` without auth dependency — backend/api/router_questionnaire.py:232
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/router_questionnaire.py:232 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_case` without auth dependency — backend/api/router_cases.py:363
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/router_cases.py:363 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `data_governance_major_city_employment_backlog_claims_update` without auth dependency — backend/api/router_data_governance.py:211
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/router_data_governance.py:211 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `patch_config` without auth dependency — backend/api/router_console.py:45
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/router_console.py:45 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `patch_expiry` without auth dependency — backend/api/router_advisor_admin.py:87
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/router_advisor_admin.py:87 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `patch_status` without auth dependency — backend/api/router_advisor_admin.py:101
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/router_advisor_admin.py:101 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `update_agent_workflow_task_claim_api` without auth dependency — backend/api/router_tools.py:329
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/router_tools.py:329 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `build_report_pdf` without auth dependency — backend/api/router_reports.py:63
`@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/router_reports.py:63 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `build_report` without auth dependency — backend/api/router_reports.py:44
`@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/router_reports.py:44 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `claim_agent_workflow_tasks_api` without auth dependency — backend/api/router_tools.py:297
`@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/router_tools.py:297 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create` without auth dependency — backend/api/router_advisor_admin.py:54
`@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/router_advisor_admin.py:54 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `data_governance_major_city_employment_backlog_claims_create` without auth dependency — backend/api/router_data_governance.py:94
`@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/router_data_governance.py:94 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `data_governance_major_city_employment_backlog_dispatch_create` without auth dependency — backend/api/router_data_governance.py:179
`@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/router_data_governance.py:179 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `data_update_run_replay` without auth dependency — backend/api/router_data_updates.py:169
`@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/router_data_updates.py:169 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `data_update_run` without auth dependency — backend/api/router_data_updates.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/api/router_data_updates.py:142 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `preference_match_post` without auth dependency — backend/api/router_preference_match.py:188
`@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/router_preference_match.py:188 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `save_agent_workflow_task_result_api` without auth dependency — backend/api/router_tools.py:254
`@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/router_tools.py:254 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `save_answers` without auth dependency — backend/api/router_questionnaire.py:208
`@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/router_questionnaire.py:208 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `save_case_holland_snapshot` without auth dependency — backend/api/router_assessments.py:79
`@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/router_assessments.py:79 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `save_model_feedback` without auth dependency — backend/api/router_tools.py:399
`@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/router_tools.py:399 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `scope_query` without auth dependency — backend/api/router_scope.py:33
`@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/router_scope.py:33 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `set_weights` without auth dependency — backend/api/router_score.py:155
`@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/router_score.py:155 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `submit_answers` without auth dependency — holland/backend/main.py:420
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
holland/backend/main.py:420 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `sync_case_holland_snapshot` without auth dependency — backend/api/router_assessments.py:96
`@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/router_assessments.py:96 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `upsert_case` without auth dependency — backend/api/router_cases.py:320
`@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/router_cases.py:320 securityAuth fastapi unauth mutation
high System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in scripts/gen_doc_facts.py:51
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
scripts/gen_doc_facts.py:51 Subprocess shell true
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/js/app_state_api.js:33
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/js/screens_tool_registry.js:719
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 — holland/frontend/js/api.js:14
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: .claude/settings.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.
.claude/settings.json VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/architecture-review/references/refactoring-patterns.md
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.
.claude/skills/architecture-review/references/refactoring-patterns.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/architecture-review/SKILL.md
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.
.claude/skills/architecture-review/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/chunkymonkey-governance/SKILL.md
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.
.claude/skills/chunkymonkey-governance/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/chunkymonkey-review-gate/SKILL.md
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.
.claude/skills/chunkymonkey-review-gate/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/code-simplifier/SKILL.md
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.
.claude/skills/code-simplifier/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/first-principles-thinking/README.md
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.
.claude/skills/first-principles-thinking/README.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/lifehack-project-workflow/references/checklist.md
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.
.claude/skills/lifehack-project-workflow/references/checklist.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/lifehack-project-workflow/SKILL.md
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.
.claude/skills/lifehack-project-workflow/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: AGENTS.md
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.
AGENTS.md VerificationAgents md
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
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 security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/console.html:76
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/console.html:76 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/data_catalog.html:70
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/data_catalog.html:70 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in holland/frontend/js/chart.js:179
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
holland/frontend/js/chart.js:179 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in holland/frontend/js/survey_config.js:66
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
holland/frontend/js/survey_config.js:66 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in holland/frontend/result.html:32
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
holland/frontend/result.html:32 Direct innerhtml assignment
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — backend/scripts/agent_handoff.py:51
`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/deployment_readiness.py:89
`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 — datahub/datahub/connectors/macos_vision_ocr.py:78
`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 — datahub/datahub/parsers/ln_score_distribution_grid_images.py:292
`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 — holland/scripts/fetch_ipip.py:27
`urllib.request.urlopen(...)` 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 — holland/scripts/fetch_onet.py:27
`urllib.request.urlopen(...)` 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/gen_doc_facts.py:51
`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/run_source.py:56
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 42 placeholder/mock markers across 17 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 1175 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 cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 22, 25
.github/workflows/phase0_no_db_gates.yml:22, 25 (2 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Tests conf 1.00 Low test-to-source ratio
72 tests / 656 src (ratio 0.11).
low System graph quality Integrity conf 1.00 15 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/api/router_console.py:configs, backend/api/router_console.py:config 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.
15 occurrences
repo-level (15 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 4 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: backend/services/model_tuning.py:save_model_tuning_run, backend/services/model_audit.py:save_model_audit_run, backend/services/model_feedback.py:save_model_feedback_run This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — se…
4 occurrences
repo-level (4 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 6 places
Functions with the same first-5-line body hash: backend/scripts/build_zhilian_salary.py:import_zhilian_salary_package, backend/scripts/build_major_setup_change.py:import_major_setup_change_package, backend/scripts/build_discipline_eval.py:import_discipline_eval_package, backend/scripts/build_school…
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_build_copy` in backend/services/report_building.py:14
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 `_build_copy` in backend/services/report_building_content.py:56
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 `_build_copy` in backend/services/report_building_support.py:8
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 `by_old` in backend/scripts/sync_schema_registry.py:304
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 `career_default_v1` in backend/tests/test_phase0.py:547
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 `career_default_v1` in datahub/datahub/builders/career_score.py:142
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 `career_default_v1` in datahub/tests/test_contract.py:7473
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 `fa_mart_case_recommendation_v2` in backend/services/recommendation/recommendation_repository.py:66
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 `family_report_template_v1` in design/screens.jsx:368
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 `industry_lifecycle_v2` in backend/services/industry_lifecycle.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 `legacy_unused` in backend/scripts/migrate_register_consultation_case_2026_05_28.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 `penetration_sw_v1` in backend/services/major_industry_penetration.py:90
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 `primary_old` in scripts/gen_feature_catalog.py:1005
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_health_prefers_yearbook_over_legacy` in backend/tests/test_city_features_health.py:51
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 `tmp_copy` in datahub/datahub/connectors/amap_transit_batch.py:59
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 `whitepaper_v1` in design/data.jsx:1
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: build_onet_candidates
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
holland/backend/question_candidates.py:170
low System graph software Dead code conf 1.00 Possibly dead Python function: compute_take_home
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/take_home_wage.py:38
low System graph software Dead code conf 1.00 Possibly dead Python function: list_tool_items
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/tool_registry.py:19
low System graph software Dead code conf 1.00 Possibly dead Python function: load_floor_by_province_industry
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/wage_caliber.py:90
low System graph software Dead code conf 1.00 Possibly dead Python function: load_latest_agent_workflow_run_summary
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/agent_workflow_registry.py:326
low System graph software Dead code conf 1.00 Possibly dead Python function: load_latest_agent_workflow_task_claims
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/agent_workflow_task_claims.py:325
low System graph software Dead code conf 1.00 Possibly dead Python function: load_latest_agent_workflow_task_results
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/agent_workflow_task_results.py:413
low System graph software Dead code conf 1.00 Possibly dead Python function: load_latest_agent_workflow_tasks
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/agent_workflow_registry.py:670
low System graph software Dead code conf 1.00 Possibly dead Python function: ping
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/chunky_bridge/__init__.py:67
low System graph software Dead code conf 1.00 Possibly dead Python function: ping
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/chunky_bridge/queries.py:417
low System graph software Dead code conf 1.00 Possibly dead Python function: rebuild_city_scores
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/city_scoring.py:26
low System graph software Dead code conf 1.00 Possibly dead Python function: reject_duplicate_keys
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/json_loader.py:21
low System graph software Dead code conf 1.00 Possibly dead Python function: reject_duplicate_keys
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
datahub/datahub/config.py:16
low System graph software Dead code conf 1.00 Possibly dead Python function: reload_configs
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/config_loader.py:137
low System graph software Dead code conf 1.00 Possibly dead Python function: require_case_questionnaire_ready
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/services/recommendation/questionnaire_gate.py:28
low System graph software Dead code conf 1.00 Possibly dead Python function: safe_float
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scripts/ingest_admission_data.py:46
low System graph software Dead code conf 1.00 Possibly dead Python function: safe_int
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/scripts/ingest_admission_data.py:55
low System graph software Dead code conf 1.00 Possibly dead Python function: write_manifest
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
datahub/datahub/exporters/package_exporter.py:18
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /{case_id}
`backend/api/router_questionnaire.py` declares `DELETE /{case_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/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 /audit
`backend/api/router_console.py` declares `GET /audit` 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 /batches
`backend/api/router_score.py` declares `GET /batches` 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 /branding
`backend/api/router_console.py` declares `GET /branding` 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 /browse/{key}
`backend/api/router_data_browse.py` declares `GET /browse/{key}` 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 /catalog
`backend/api/router_data.py` declares `GET /catalog` 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 /companies
`backend/api/router_city.py` declares `GET /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 /compare
`backend/api/router_city.py` declares `GET /compare` 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 /config
`backend/api/router_questionnaire.py` declares `GET /config` 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 /config/{key}
`backend/api/router_console.py` declares `GET /config/{key}` 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 /configs
`backend/api/router_console.py` declares `GET /configs` 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 /facets
`backend/api/router_scope.py` declares `GET /facets` 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 /history/{school_code}
`backend/api/router_score.py` declares `GET /history/{school_code}` 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 /lineage
`backend/api/router_data_lineage.py` declares `GET /lineage` 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 /overview
`backend/api/router_industry.py` declares `GET /overview` 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 /profile/{adcode}
`backend/api/router_city.py` declares `GET /profile/{adcode}` 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 /profile/{major_code}
`backend/api/router_major.py` declares `GET /profile/{major_code}` 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 /profile/{occupation_code}
`backend/api/router_occupation.py` declares `GET /profile/{occupation_code}` 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 /profile/{sw_l2}
`backend/api/router_industry.py` declares `GET /profile/{sw_l2}` 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 /recommend
`backend/api/router_score.py` declares `GET /recommend` 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 /schools/search
`backend/api/router_score.py` declares `GET /schools/search` 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 /search
`backend/api/router_occupation.py` declares `GET /search` 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 /stats
`backend/api/router_data_stats.py` declares `GET /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 /strength
`backend/api/router_major.py` declares `GET /strength` 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
`backend/api/router_city.py` declares `GET /top` 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 /weights
`backend/api/router_score.py` declares `GET /weights` 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 /{advisor_id}
`backend/api/router_advisor_admin.py` declares `GET /{advisor_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 /{case_id}
`backend/api/router_questionnaire.py` declares `GET /{case_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 /{case_id}/analysis
`backend/api/router_questionnaire.py` declares `GET /{case_id}/analysis` 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 /{case_id}/preference-match
`backend/api/router_preference_match.py` declares `GET /{case_id}/preference-match` 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 /{case_id}/preference-match/diff
`backend/api/router_preference_match.py` declares `GET /{case_id}/preference-match/diff` 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 /{case_id}/preference-match/snapshots
`backend/api/router_preference_match.py` declares `GET /{case_id}/preference-match/snapshots` 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 w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{case_id}/revisit
`backend/api/router_reports.py` declares `GET /{case_id}/revisit` 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 /{case_id}/revisit/snapshots
`backend/api/router_reports.py` declares `GET /{case_id}/revisit/snapshots` 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 /{key}
`backend/api/router_config.py` declares `GET /{key}` 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 /{major_code}/industry
`backend/api/router_major.py` declares `GET /{major_code}/industry` 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 /{run_id}/source-health
`backend/api/router_data_updates.py` declares `GET /{run_id}/source-health` 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 /{run_id}/steps
`backend/api/router_data_updates.py` declares `GET /{run_id}/steps` 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 /config/{key}
`backend/api/router_console.py` declares `PATCH /config/{key}` 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 /{advisor_id}/expiry
`backend/api/router_advisor_admin.py` declares `PATCH /{advisor_id}/expiry` 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 /{advisor_id}/status
`backend/api/router_advisor_admin.py` declares `PATCH /{advisor_id}/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: POST /
`backend/api/router_advisor_admin.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: POST /replay
`backend/api/router_data_updates.py` declares `POST /replay` 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 /run
`backend/api/router_data_updates.py` declares `POST /run` 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 /weights
`backend/api/router_score.py` declares `POST /weights` 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 /{case_id}
`backend/api/router_questionnaire.py` declares `POST /{case_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: POST /{case_id}/build
`backend/api/router_reports.py` declares `POST /{case_id}/build` 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 /{case_id}/pdf
`backend/api/router_reports.py` declares `POST /{case_id}/pdf` 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 /{case_id}/preference-match
`backend/api/router_preference_match.py` declares `POST /{case_id}/preference-match` 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 quality Complexity conf 1.00 Very large file: backend/tests/test_phase0.py (12762 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: datahub/tests/test_contract.py (17373 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/js/screens_data.js (1588 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/js/screens_reportpage.js (1045 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/js/screens_tool_registry.js (2385 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/cb7ebc15-b6e4-4b56-8615-0d3456c510b4/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/cb7ebc15-b6e4-4b56-8615-0d3456c510b4/

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.