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

wyl2607/esg-research-toolkit

https://github.com/wyl2607/esg-research-toolkit · scanned 2026-06-16 01:01 UTC (2 months, 1 week ago)

152 raw signals (0 security + 152 graph)

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

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 117 actionable findings from 1 signal source. 35 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
59.3
/100
Security checks
59
0 findings
System graph
59
100.0% cov · 117 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 14 Medium 9 Low 81 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 117 Crowd 0 Layer: Software 19 Frontend 11 Hardware 2 Security 16 Cicd 2 Quality 24 Api 43
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 59.3/100 with 100.0% coverage. It contains 1770 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 152 findings — concentrated in api (43), quality (42), software (19). Risk profile is high: 0 critical, 14 high, 24 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 104 of 117 actionable findings. 152 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 security auth conf 1.00 FastAPI POST `clear_framework_cache` without auth dependency — esg_frameworks/api.py:272
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
esg_frameworks/api.py:272 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `full_report` without auth dependency — taxonomy_scorer/api.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.
taxonomy_scorer/api.py:44 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `lcoe` without auth dependency — techno_economics/api.py:11
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
techno_economics/api.py:11 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `preview_merge` without auth dependency — report_parser/api.py:544
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
report_parser/api.py:544 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `recompute` without auth dependency — benchmark/api.py:11
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
benchmark/api.py:11 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `saf_cost` without auth dependency — techno_economics/api.py:92
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
techno_economics/api.py:92 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `save_manual_report` without auth dependency — report_parser/api.py:518
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
report_parser/api.py:518 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `score_from_data` without auth dependency — esg_frameworks/api.py:144
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
esg_frameworks/api.py:144 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `score` without auth dependency — taxonomy_scorer/api.py:38
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
taxonomy_scorer/api.py:38 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `sensitivity` without auth dependency — techno_economics/api.py:17
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
techno_economics/api.py:17 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `text_report` without auth dependency — taxonomy_scorer/api.py:52
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
taxonomy_scorer/api.py:52 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `upload_report` without auth dependency — report_parser/api.py:406
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
report_parser/api.py:406 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `upload_report` without auth dependency — report_parser/api.py:513
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
report_parser/api.py:513 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `upload_reports_batch` without auth dependency — report_parser/api.py:476
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
report_parser/api.py:476 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/scripts/frontend-health-check.mjs:372
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/lib/api.ts:45
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph quality Integrity conf 1.00 15 occurrences Frontend route `upload` 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.
15 occurrences
repo-level (15 hits)
Orphan pageWiring
medium System graph cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned
appleboy/[email protected] can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 2 locations
.github/workflows/deploy.yml:35
.github/workflows/docker.yml:18
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in frontend/scripts/frontend-health-check.mjs:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
frontend/scripts/frontend-health-check.mjs:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in scripts/automation/benchmark_windows_node.sh:39
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
scripts/automation/benchmark_windows_node.sh:39 Subprocess shell true
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/dev_tasks/05_commit_readiness.py:140
`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 Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 50 placeholder/mock markers across 22 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 Integrity conf 1.00 27 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `API_BASE`, `API_BASE_URL`, `BACKFILL_HTTP_TIMEOUT`, `BACKFILL_POLL_INTERVAL`, `BACKFILL_POLL_TIMEOUT`, `CI`, `DEPLOY_FINGERPRINT_PATH`, `DEV` + 19 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 290 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 2 occurrences Docker base image is tag-pinned but not digest-pinned: python:3.12-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 1, 9
Dockerfile:1, 9 (2 hits)
containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 16 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
6 files, 16 locations
.github/workflows/contracts.yml:18, 21, 26, 120 (4 hits)
.github/workflows/frontend-health-check.yml:18, 21, 26, 64 (4 hits)
.github/workflows/test.yml:19, 56, 61, 95 (4 hits)
.github/workflows/lint.yml:15, 44 (2 hits)
.github/workflows/deploy.yml:18
.github/workflows/repo-guard.yml:19
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 5 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: scripts/extraction_qa_audit.py:audit_level_1, scripts/extraction_qa_audit.py:audit_level_2 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.
5 occurrences
repo-level (5 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: esg_frameworks/sasb_standards.py:score_sasb, esg_frameworks/sec_climate.py:score_sec_climate, esg_frameworks/gri_standards.py:score_gri This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene).…
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `company_profile_v1` in tests/test_profile_contract.py:19
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 esg_frameworks/api.py:96
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 report_parser/storage.py:118
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 taxonomy_scorer/scorer.py:81
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 techno_economics/sensitivity.py:40
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 tests/test_frameworks_comparison.py:216
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 tests/test_report_parser.py:462
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 `remaining_legacy` in scripts/migrate_canonical_company_names.py:123
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 `report_parser_v1` in report_parser/api.py:49
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: act_api_health
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/automation/interactive_dev.py:101
low System graph software Dead code conf 1.00 Possibly dead Python function: act_benchmarks_recompute
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/automation/interactive_dev.py:208
low System graph software Dead code conf 1.00 Possibly dead Python function: act_db_summary
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/automation/interactive_dev.py:54
low System graph software Dead code conf 1.00 Possibly dead Python function: act_frontend_build
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/automation/interactive_dev.py:175
low System graph software Dead code conf 1.00 Possibly dead Python function: act_frontend_lint
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/automation/interactive_dev.py:171
low System graph software Dead code conf 1.00 Possibly dead Python function: act_frontend_smoke
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/automation/interactive_dev.py:179
low System graph software Dead code conf 1.00 Possibly dead Python function: act_git_status
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/automation/interactive_dev.py:183
low System graph software Dead code conf 1.00 Possibly dead Python function: act_open_browser
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/automation/interactive_dev.py:218
low System graph software Dead code conf 1.00 Possibly dead Python function: act_pytest_fast
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/automation/interactive_dev.py:157
low System graph software Dead code conf 1.00 Possibly dead Python function: act_pytest_full
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/automation/interactive_dev.py:161
low System graph software Dead code conf 1.00 Possibly dead Python function: act_seed_status
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/automation/interactive_dev.py:187
low System graph software Dead code conf 1.00 Possibly dead Python function: act_trend_peek
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/automation/interactive_dev.py:123
low System graph software Dead code conf 1.00 Possibly dead Python function: act_ui_screenshots
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/automation/interactive_dev.py:223
low System graph software Dead code conf 1.00 Possibly dead Python function: custom_openapi
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
main.py:391
low System graph software Dead code conf 1.00 Possibly dead Python function: report_quality_score
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
report_parser/company_identity.py:80
low System graph software Dead code conf 1.00 Possibly dead Python function: score_gri
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
esg_frameworks/gri_standards.py:129
low System graph software Dead code conf 1.00 Possibly dead Python function: score_sasb
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
esg_frameworks/sasb_standards.py:113
low System graph software Dead code conf 1.00 Possibly dead Python function: score_sec_climate
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
esg_frameworks/sec_climate.py:124
low System graph software Dead code conf 1.00 Possibly dead Python function: wrap
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
taxonomy_scorer/pdf_report.py:84
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 api Wiring conf 1.00 Unused endpoint: DELETE /companies/{company_name}/{report_year:int}
`report_parser/admin_routes.py` declares `DELETE /companies/{company_name}/{report_year:int}` 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 /
`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 /activities
`taxonomy_scorer/api.py` declares `GET /activities` 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 /benchmarks
`techno_economics/api.py` declares `GET /benchmarks` 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
`report_parser/api.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 /companies/by-industry/{industry_code}
`report_parser/api.py` declares `GET /companies/by-industry/{industry_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 /companies/export/csv
`report_parser/admin_routes.py` declares `GET /companies/export/csv` 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/export/xlsx
`report_parser/admin_routes.py` declares `GET /companies/export/xlsx` 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/v2
`report_parser/api.py` declares `GET /companies/v2` 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/{company_name}/history
`report_parser/api.py` declares `GET /companies/{company_name}/history` 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/{company_name}/profile
`report_parser/api.py` declares `GET /companies/{company_name}/profile` 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/{company_name}/{report_year:int}
`report_parser/api.py` declares `GET /companies/{company_name}/{report_year:int}` 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 /compare
`esg_frameworks/api.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 /compare/regional
`esg_frameworks/api.py` declares `GET /compare/regional` 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 /dashboard/stats
`report_parser/api.py` declares `GET /dashboard/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 /jobs/{batch_id}
`report_parser/api.py` declares `GET /jobs/{batch_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 /lane-stats
`report_parser/disclosures_api.py` declares `GET /lane-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 /list
`esg_frameworks/api.py` declares `GET /list` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /pending
`report_parser/disclosures_api.py` declares `GET /pending` 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 /report
`taxonomy_scorer/api.py` declares `GET /report` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /report/pdf
`taxonomy_scorer/api.py` declares `GET /report/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: GET /results
`esg_frameworks/api.py` declares `GET /results` 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 /results/{result_id}
`esg_frameworks/api.py` declares `GET /results/{result_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 /score
`esg_frameworks/api.py` declares `GET /score` 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 /{company_report_id:int}/audit-trail
`report_parser/api.py` declares `GET /{company_report_id:int}/audit-trail` 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_code}
`benchmark/api.py` declares `GET /{industry_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: POST /cache/clear
`esg_frameworks/api.py` declares `POST /cache/clear` 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 /companies/{company_name}/{report_year:int}/request-deletion
`report_parser/admin_routes.py` declares `POST /companies/{company_name}/{report_year:int}/request-deletion` 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 o…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /fetch
`report_parser/disclosures_api.py` declares `POST /fetch` 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 /lcoe
`techno_economics/api.py` declares `POST /lcoe` 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 /manual
`report_parser/api.py` declares `POST /manual` 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 /merge/preview
`report_parser/api.py` declares `POST /merge/preview` 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 /recompute
`benchmark/api.py` declares `POST /recompute` 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 /report
`taxonomy_scorer/api.py` declares `POST /report` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /report/text
`taxonomy_scorer/api.py` declares `POST /report/text` 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 /saf
`techno_economics/api.py` declares `POST /saf` 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 /score
`taxonomy_scorer/api.py` declares `POST /score` 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 /score/upload
`esg_frameworks/api.py` declares `POST /score/upload` 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 /sensitivity
`techno_economics/api.py` declares `POST /sensitivity` 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 /upload
`report_parser/api.py` declares `POST /upload` 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 /upload/batch
`report_parser/api.py` declares `POST /upload/batch` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{pending_id}/approve
`report_parser/disclosures_api.py` declares `POST /{pending_id}/approve` 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 /{pending_id}/reject
`report_parser/disclosures_api.py` declares `POST /{pending_id}/reject` 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: frontend/src/lib/types.ts (4036 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/test_report_parser.py (2846 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/802e6166-c17e-42af-9224-8905300b642a/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/802e6166-c17e-42af-9224-8905300b642a/

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.