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

twonezerotwo-hue/clean-e-yay

https://github.com/twonezerotwo-hue/clean-e-yay · scanned 2026-06-16 00:44 UTC (2 months, 1 week ago)

80 raw signals (0 security + 80 graph)

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

Complete repo analysis

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

JSON
Combined
81.3
/100
Security checks
81
0 findings
System graph
81
88.9% cov · 77 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 5 Low 50 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 77 Crowd 0 Layer: Software 2 Frontend 5 Security 16 Quality 20 Api 34
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 81.3/100 with 88.9% coverage. It contains 1583 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 80 findings — concentrated in api (34), quality (23), security (16). Risk profile is high: 0 critical, 14 high, 5 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 69 of 77 actionable findings. 80 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 `approve_manual_ready` without auth dependency — apps/api/routers/paper_trading.py:218
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/routers/paper_trading.py:218 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `dismiss_manual_ready` without auth dependency — apps/api/routers/paper_trading.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.
apps/api/routers/paper_trading.py:254 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_approve` without auth dependency — apps/api/routers/rebalance.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.
apps/api/routers/rebalance.py:54 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_chat` without auth dependency — apps/api/routers/chat.py:25
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/routers/chat.py:25 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_halts_reset` without auth dependency — apps/api/routers/risk.py:47
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/routers/risk.py:47 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_maintenance_archive` without auth dependency — apps/api/routers/paper_trading.py:280
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/routers/paper_trading.py:280 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_maintenance_repair` without auth dependency — apps/api/routers/paper_trading.py:286
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/routers/paper_trading.py:286 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_maintenance_reset` without auth dependency — apps/api/routers/paper_trading.py:292
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/routers/paper_trading.py:292 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_paper_tick` without auth dependency — apps/api/routers/paper_trading.py:97
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/routers/paper_trading.py:97 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_propose` without auth dependency — apps/api/routers/rebalance.py:43
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/routers/rebalance.py:43 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_reject` without auth dependency — apps/api/routers/rebalance.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.
apps/api/routers/rebalance.py:63 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_retrain_calibration` without auth dependency — apps/api/routers/learning.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.
apps/api/routers/learning.py:44 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `reject_manual_ready` without auth dependency — apps/api/routers/paper_trading.py:244
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/routers/paper_trading.py:244 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `reset` without auth dependency — apps/api/routers/paper_trading.py:265
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
apps/api/routers/paper_trading.py:265 securityAuth fastapi unauth mutation
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 'cors_wildcard' in apps/api/main.py:52
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
apps/api/main.py:52 Cors wildcard
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/codegen.py:59
`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 40 placeholder/mock markers across 19 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 6 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 quality Tests conf 1.00 Low test-to-source ratio
37 tests / 164 src (ratio 0.23).
low System graph quality Integrity conf 1.00 4 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: apps/api/routers/decision.py:get_decision_matrix, apps/api/routers/cockpit.py:get_cockpit_brief 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 sep…
4 occurrences
repo-level (4 hits)
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 `_seed_v2` in tests/unit/test_learning_outcomes.py:213
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 `is_v2` in packages/learning/fingerprint.py:55
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 `is_v2` in tests/unit/test_timeframe_contracts.py:99
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 packages/risk/event_risk.py:132
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `touche_fallback_legacy` in packages/consensus/engine.py:78
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 `weights_v1` in apps/api/routers/rebalance.py:5
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `weights_v1` in tests/unit/test_rebalance.py:5
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: outcome_to_dict
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
packages/learning/outcomes.py:125
low System graph software Dead code conf 1.00 Possibly dead Python function: summarize
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
packages/learning/walkforward.py:27
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — apps/web/hooks/useOwnerFeedback.ts:17
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: GET /ai-report/current
`apps/api/routers/ai_report.py` declares `GET /ai-report/current` 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 /cockpit/brief
`apps/api/routers/cockpit.py` declares `GET /cockpit/brief` 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/state
`apps/api/routers/dashboard_state.py` declares `GET /dashboard/state` 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 /data/snapshot
`apps/api/routers/data.py` declares `GET /data/snapshot` 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 /decision/matrix
`apps/api/routers/decision.py` declares `GET /decision/matrix` 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 /learning/calibration
`apps/api/routers/learning.py` declares `GET /learning/calibration` 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 /learning/mistakes
`apps/api/routers/learning.py` declares `GET /learning/mistakes` 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 /learning/rebalance/proposal
`apps/api/routers/rebalance.py` declares `GET /learning/rebalance/proposal` 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 /learning/summary
`apps/api/routers/learning.py` declares `GET /learning/summary` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /paper-trading/manual-ready
`apps/api/routers/paper_trading.py` declares `GET /paper-trading/manual-ready` 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 /paper-trading/state
`apps/api/routers/paper_trading.py` declares `GET /paper-trading/state` 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 /regime-report/current
`apps/api/routers/regime_report.py` declares `GET /regime-report/current` 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 /replay/backtest
`apps/api/routers/replay.py` declares `GET /replay/backtest` 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 /replay/backtest/{run_id}
`apps/api/routers/replay.py` declares `GET /replay/backtest/{run_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 /replay/status
`apps/api/routers/replay.py` declares `GET /replay/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /replay/{snapshot_id}
`apps/api/routers/replay.py` declares `GET /replay/{snapshot_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 /replay/{snapshot_id}/decision-trace
`apps/api/routers/replay.py` declares `GET /replay/{snapshot_id}/decision-trace` 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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /risk/correlation
`apps/api/routers/risk.py` declares `GET /risk/correlation` 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 /risk/halts
`apps/api/routers/risk.py` declares `GET /risk/halts` 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 /system/health
`apps/api/routers/system.py` declares `GET /system/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: POST /chat
`apps/api/routers/chat.py` declares `POST /chat` 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 /learning/calibration/retrain
`apps/api/routers/learning.py` declares `POST /learning/calibration/retrain` 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 /learning/rebalance/approve
`apps/api/routers/rebalance.py` declares `POST /learning/rebalance/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 /learning/rebalance/propose
`apps/api/routers/rebalance.py` declares `POST /learning/rebalance/propose` 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 /learning/rebalance/reject
`apps/api/routers/rebalance.py` declares `POST /learning/rebalance/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 api Wiring conf 1.00 Unused endpoint: POST /paper-trading/maintenance/archive
`apps/api/routers/paper_trading.py` declares `POST /paper-trading/maintenance/archive` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /paper-trading/maintenance/repair
`apps/api/routers/paper_trading.py` declares `POST /paper-trading/maintenance/repair` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /paper-trading/maintenance/reset
`apps/api/routers/paper_trading.py` declares `POST /paper-trading/maintenance/reset` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /paper-trading/manual-ready/{manual_id}/approve
`apps/api/routers/paper_trading.py` declares `POST /paper-trading/manual-ready/{manual_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 documen…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /paper-trading/manual-ready/{manual_id}/dismiss
`apps/api/routers/paper_trading.py` declares `POST /paper-trading/manual-ready/{manual_id}/dismiss` 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 documen…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /paper-trading/manual-ready/{manual_id}/reject
`apps/api/routers/paper_trading.py` declares `POST /paper-trading/manual-ready/{manual_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 document…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /paper-trading/reset
`apps/api/routers/paper_trading.py` declares `POST /paper-trading/reset` 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 /paper-trading/tick
`apps/api/routers/paper_trading.py` declares `POST /paper-trading/tick` 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 /risk/halts/reset
`apps/api/routers/risk.py` declares `POST /risk/halts/reset` 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: apps/web/types/generated/schema.ts (2398 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/1e7f17f6-2626-4fb6-9d5d-13f5ff18f14f/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/1e7f17f6-2626-4fb6-9d5d-13f5ff18f14f/

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.