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

sevnightingale/plutus-agent

https://github.com/sevnightingale/plutus-agent · scanned 2026-06-16 00:08 UTC (2 months, 2 weeks ago)

356 raw signals (0 security + 356 graph)

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

Complete repo analysis

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

JSON
Combined
61.1
/100
Security checks
61
0 findings
System graph
61
100.0% cov · 335 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 27 Medium 17 Low 192 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 335 Crowd 0 Layer: Software 24 Frontend 2 Hardware 1 Security 30 Cicd 1 Quality 227 Api 50
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 61.1/100 with 100.0% coverage. It contains 24398 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 356 findings — concentrated in quality (243), api (50), security (30). Risk profile is high: 0 critical, 27 high, 17 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 236 of 335 actionable findings. 356 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 quality Integrity conf 1.00 Blocking `time.sleep(...)` inside `async def start_gateway` — harness/gateway/run.py:11065
Sync I/O inside an async function blocks the event loop. While `time.sleep(...)` is running, *all* other coroutines on this loop are paused — silent throughput collapse under concurrency. Use the async equivalent (`httpx.AsyncClient`, `asyncio.sleep`, `aiofiles`) or wrap with `await asyncio.to_thre…
harness/gateway/run.py:11065 Sync io in asyncPerformance
high System graph quality Integrity conf 1.00 Blocking `time.sleep(...)` inside `async def start_gateway` — harness/gateway/run.py:11076
Sync I/O inside an async function blocks the event loop. While `time.sleep(...)` is running, *all* other coroutines on this loop are paused — silent throughput collapse under concurrency. Use the async equivalent (`httpx.AsyncClient`, `asyncio.sleep`, `aiofiles`) or wrap with `await asyncio.to_thre…
harness/gateway/run.py:11076 Sync io in asyncPerformance
high System graph security auth conf 1.00 FastAPI DELETE `cancel_oauth_session` without auth dependency — harness/cli/web_server.py:1895
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
harness/cli/web_server.py:1895 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_cron_job` without auth dependency — harness/cli/web_server.py:2088
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
harness/cli/web_server.py:2088 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_session_endpoint` without auth dependency — harness/cli/web_server.py:1939
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
harness/cli/web_server.py:1939 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `disconnect_oauth_provider` without auth dependency — harness/cli/web_server.py:1293
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
harness/cli/web_server.py:1293 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `remove_env_var` without auth dependency — harness/cli/web_server.py:1001
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
harness/cli/web_server.py:1001 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_cron_job` without auth dependency — harness/cli/web_server.py:2040
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
harness/cli/web_server.py:2040 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `pause_cron_job` without auth dependency — harness/cli/web_server.py:2061
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
harness/cli/web_server.py:2061 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `restart_gateway` without auth dependency — harness/cli/web_server.py:659
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
harness/cli/web_server.py:659 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `resume_cron_job` without auth dependency — harness/cli/web_server.py:2070
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
harness/cli/web_server.py:2070 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `reveal_env_var` without auth dependency — harness/cli/web_server.py:1015
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
harness/cli/web_server.py:1015 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `start_oauth_login` without auth dependency — harness/cli/web_server.py:1835
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
harness/cli/web_server.py:1835 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `submit_oauth_code` without auth dependency — harness/cli/web_server.py:1867
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
harness/cli/web_server.py:1867 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trigger_cron_job` without auth dependency — harness/cli/web_server.py:2079
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
harness/cli/web_server.py:2079 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `update_hermes` without auth dependency — harness/cli/web_server.py:674
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
harness/cli/web_server.py:674 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `set_dashboard_theme` without auth dependency — harness/cli/web_server.py:2599
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
harness/cli/web_server.py:2599 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `set_env_var` without auth dependency — harness/cli/web_server.py:991
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
harness/cli/web_server.py:991 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `toggle_skill` without auth dependency — harness/cli/web_server.py:2118
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
harness/cli/web_server.py:2118 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_config_raw` without auth dependency — harness/cli/web_server.py:2180
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
harness/cli/web_server.py:2180 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_config` without auth dependency — harness/cli/web_server.py:962
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
harness/cli/web_server.py:962 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_cron_job` without auth dependency — harness/cli/web_server.py:2052
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
harness/cli/web_server.py:2052 securityAuth fastapi unauth mutation
high System graph security security conf 1.00 Insecure pattern 'eval_used' in harness/tools/skills_guard.py:294
Found a known-risky pattern (eval_used). Review and replace if possible.
harness/tools/skills_guard.py:294 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in skills/software-development/requesting-code-review/SKILL.md:146
Found a known-risky pattern (eval_used). Review and replace if possible.
skills/software-development/requesting-code-review/SKILL.md:146 Eval used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in harness/cli/tips.py:304
Found a known-risky pattern (exec_used). Review and replace if possible.
harness/cli/tips.py:304 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in harness/tools/skills_guard.py:297
Found a known-risky pattern (exec_used). Review and replace if possible.
harness/tools/skills_guard.py:297 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in skills/software-development/requesting-code-review/SKILL.md:146
Found a known-risky pattern (exec_used). Review and replace if possible.
skills/software-development/requesting-code-review/SKILL.md:146 Exec used
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 skills/software-development/requesting-code-review/SKILL.md:258
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
skills/software-development/requesting-code-review/SKILL.md:258 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in harness/repl.py:6179
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
harness/repl.py:6179 Subprocess shell true
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in harness/tools/environments/docker.py:566
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
harness/tools/environments/docker.py:566 Subprocess shell true
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in harness/tools/transcription_tools.py:410
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
harness/tools/transcription_tools.py:410 Subprocess shell true
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in skills/software-development/requesting-code-review/SKILL.md:61
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
skills/software-development/requesting-code-review/SKILL.md:61 Subprocess shell true
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — harness/cli/config.py:3805
`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 — harness/cli/main.py:891
`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 — harness/cli/setup.py:912
`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 — harness/cli/tools_config.py:385
`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 — harness/cli/uninstall.py:176
`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 — harness/cli/web_server.py:640
`subprocess.Popen(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — harness/tools/transcription_tools.py:410
`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/contributor_audit.py:77
`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/release.py:451
`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 24 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration
A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.
Runtime configService clientGenerated repo pattern
low System graph quality Integrity conf 1.00 270 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ACP_AGENT_WALLET`, `AI_GATEWAY_API_KEY`, `AI_GATEWAY_BASE_URL`, `ANTHROPIC_API_KEY`, `ANTHROPIC_TOKEN`, `API_SERVER_CORS_ORIGINS`, `API_SERVER_ENABLED`, `API_SERVER_HOST` + 262 more. Add them (with a placeholder/comment) to .env.example so onboard…
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 3258 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 Integrity conf 1.00 Near-duplicate function bodies in 10 places
Functions with the same first-5-line body hash: trading/integrations/ta/preprocessors/ema.py:to_native, trading/integrations/ta/preprocessors/bbands.py:to_native, trading/integrations/ta/preprocessors/macd.py:to_native, trading/integrations/ta/preprocessors/atr.py:to_native This is *the* AI-coder …
duplicatesduplication
low System graph quality Integrity conf 1.00 14 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: trading/integrations/dgclaw/data_points.py:dgclaw_forums, trading/integrations/dgclaw/data_points.py:dgclaw_forum This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or docume…
14 occurrences
repo-level (14 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: trading/integrations/ta/preprocessors/psar.py:to_native, trading/integrations/ta/preprocessors/obv.py:to_native, trading/integrations/ta/preprocessors/aroon.py:to_native This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — s…
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: trading/perception/core/identity_registry.py:reset, trading/perception/core/venue_registry.py:reset, trading/perception/core/data_point_registry.py:reset, trading/perception/core/event_registry.py:reset This is *the* AI-coder failure mode (4× more du…
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_add_v1` in harness/cli/main.py:2539
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 `_call_tool_unused` in tests/tools/test_mcp_circuit_breaker.py:201
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 `_scope_my_pkg_v2` in tests/tools/test_mcp_tool.py:3007
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 `another_old` in tests/gateway/test_voice_mode_platform_isolation.py:176
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 `cfg_backup` in harness/log.py:209
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 `children_copy` in harness/run_agent.py:3572
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 `clawhub_catalog_v1` in harness/tools/skills_hub.py:1707
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 `clawhub_catalog_v1` in tests/tools/test_search_hidden_dirs.py:4
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `config_copy` in tests/cli/test_cli_provider_resolution.py:221
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 `deleted_user_copy` in harness/tools/skills_sync.py:369
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 `eleven_multilingual_v2` in harness/cli/config.py:639
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 `eleven_multilingual_v2` in harness/tools/tts_tool.py:94
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 `env_backup` in tests/tools/test_code_execution.py:606
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 `expected_legacy` in tests/tools/test_delegate.py:1443
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 `fake_legacy` in tests/cron/test_scheduler_synthetic.py:102
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 `files_upload_v2` in harness/gateway/platforms/slack.py:456
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 `files_upload_v2` in tests/gateway/test_send_image_file.py:328
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 `files_upload_v2` in tests/gateway/test_slack.py:188
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_old` in harness/cron/jobs.py:623
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 `mock_copy` in tests/cli/test_cli_copy_command.py:28
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 `proc_old` in tests/tools/test_process_registry.py:263
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `run_backup` in harness/cli/backup.py:114
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `run_backup` in tests/cli/test_backup.py:137
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 `s_old` in tests/agent/test_insights.py:127
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 `sess_old` in tests/gateway/test_mirror.py:43
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 `sess_v1` in tests/gateway/test_resume_command.py:165
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 `sid_legacy` in tests/gateway/test_async_memory_flush.py:241
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 `sig_old` in tests/agent/test_anthropic_adapter.py:1380
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 `sig_old` in tests/gateway/test_agent_cache.py:351
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_corrupt_owner_pid_falls_back_to_legacy` in tests/tools/test_browser_orphan_reaper.py:243
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_custom_max_size_and_backup` in tests/test_logging.py:130
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_elevenlabs_default_model_multilingual_v2` in tests/tools/test_tts_max_text_length.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 `test_env_override_wins_over_legacy` in tests/cli/test_api_key_providers.py:861
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_fetch_snapshots_to_v2` in tests/trading/test_dispatchers_v2.py:42
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_migration_from_v2` in tests/test_state.py:1184
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_new_platforms_takes_precedence_over_legacy` in tests/gateway/test_display_config.py:105
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_no_assistant_returns_copy` in tests/run_agent/test_run_agent.py:544
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_plain_text_uses_markdown_v2` in tests/tools/test_send_message_tool.py:489
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_read_returns_copy` in tests/tools/test_todo_tool.py:20
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_returns_deep_copy` in tests/agent/test_prompt_caching.py:73
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_switch_to_minimax_m27_strips_v1` in tests/cli/test_model_switch_opencode_anthropic.py:80
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_write_and_read_roundtrip_v2` in tests/tools/test_skills_sync.py:30
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `user_legacy` in tests/cli/test_gateway_service.py:1712
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 `very_old` in tests/cli/test_debug.py:866
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 cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts
preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.
package.json CI/CD securitySupply chainNpm
low System graph software Dead code conf 1.00 Possibly dead Python function: calc_adx
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
trading/integrations/ta/_calc.py:92
low System graph software Dead code conf 1.00 Possibly dead Python function: calc_aroon
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
trading/integrations/ta/_calc.py:103
low System graph software Dead code conf 1.00 Possibly dead Python function: calc_atr
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
trading/integrations/ta/_calc.py:197
low System graph software Dead code conf 1.00 Possibly dead Python function: calc_bbands
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
trading/integrations/ta/_calc.py:158
low System graph software Dead code conf 1.00 Possibly dead Python function: calc_bbwidth
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
trading/integrations/ta/_calc.py:168
low System graph software Dead code conf 1.00 Possibly dead Python function: calc_cci
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
trading/integrations/ta/_calc.py:57
low System graph software Dead code conf 1.00 Possibly dead Python function: calc_donchian
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
trading/integrations/ta/_calc.py:188
low System graph software Dead code conf 1.00 Possibly dead Python function: calc_ema
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
trading/integrations/ta/_calc.py:140
low System graph software Dead code conf 1.00 Possibly dead Python function: calc_keltner
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
trading/integrations/ta/_calc.py:175
low System graph software Dead code conf 1.00 Possibly dead Python function: calc_macd
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
trading/integrations/ta/_calc.py:81
low System graph software Dead code conf 1.00 Possibly dead Python function: calc_mfi
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
trading/integrations/ta/_calc.py:64
low System graph software Dead code conf 1.00 Possibly dead Python function: calc_obv
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
trading/integrations/ta/_calc.py:206
low System graph software Dead code conf 1.00 Possibly dead Python function: calc_roc
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
trading/integrations/ta/_calc.py:72
low System graph software Dead code conf 1.00 Possibly dead Python function: calc_rsi
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
trading/integrations/ta/_calc.py:35
low System graph software Dead code conf 1.00 Possibly dead Python function: calc_sma
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
trading/integrations/ta/_calc.py:133
low System graph software Dead code conf 1.00 Possibly dead Python function: calc_stochastic
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
trading/integrations/ta/_calc.py:41
low System graph software Dead code conf 1.00 Possibly dead Python function: calc_vortex
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
trading/integrations/ta/_calc.py:122
low System graph software Dead code conf 1.00 Possibly dead Python function: calc_vwap
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
trading/integrations/ta/_calc.py:147
low System graph software Dead code conf 1.00 Possibly dead Python function: calc_williams_r
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
trading/integrations/ta/_calc.py:50
low System graph software Dead code conf 1.00 Possibly dead Python function: crawl_source
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/build_skills_index.py:66
low System graph software Dead code conf 1.00 Possibly dead Python function: hl_place_trigger
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
trading/integrations/hyperliquid/venue.py:497
low System graph software Dead code conf 1.00 Possibly dead Python function: is_preprocessor_available
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
trading/integrations/ta/preprocessors/__init__.py:68
low System graph software Dead code conf 1.00 Possibly dead Python function: list_available_preprocessors
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
trading/integrations/ta/preprocessors/__init__.py:72
low System graph software Dead code conf 1.00 6 occurrences Possibly dead Python function: to_compact
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
6 files, 6 locations
trading/integrations/ta/preprocessors/bbands.py:568
trading/integrations/ta/preprocessors/donchian.py:518
trading/integrations/ta/preprocessors/ema.py:583
trading/integrations/ta/preprocessors/rsi.py:336
trading/integrations/ta/preprocessors/trix.py:497
trading/integrations/ta/preprocessors/vortex.py:648
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/whatsapp-bridge/bridge.js:150
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph quality Integrity conf 1.00 Stub function `handle_app_mention` (body is just `pass`/`return`) — harness/gateway/platforms/slack.py:199
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph quality Integrity conf 1.00 Stub function `print` (body is just `pass`/`return`) — harness/cli/skills_hub.py:569
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/cron/jobs/{job_id}
`harness/cli/web_server.py` declares `DELETE /api/cron/jobs/{job_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: DELETE /api/env
`harness/cli/web_server.py` declares `DELETE /api/env` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/providers/oauth/sessions/{session_id}
`harness/cli/web_server.py` declares `DELETE /api/providers/oauth/sessions/{session_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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/providers/oauth/{provider_id}
`harness/cli/web_server.py` declares `DELETE /api/providers/oauth/{provider_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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/sessions/{session_id}
`harness/cli/web_server.py` declares `DELETE /api/sessions/{session_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/actions/{name}/status
`harness/cli/web_server.py` declares `GET /api/actions/{name}/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/analytics/usage
`harness/cli/web_server.py` declares `GET /api/analytics/usage` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/config
`harness/cli/web_server.py` declares `GET /api/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 /api/config/defaults
`harness/cli/web_server.py` declares `GET /api/config/defaults` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/config/raw
`harness/cli/web_server.py` declares `GET /api/config/raw` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/config/schema
`harness/cli/web_server.py` declares `GET /api/config/schema` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/cron/jobs
`harness/cli/web_server.py` declares `GET /api/cron/jobs` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/cron/jobs/{job_id}
`harness/cli/web_server.py` declares `GET /api/cron/jobs/{job_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/dashboard/plugins
`harness/cli/web_server.py` declares `GET /api/dashboard/plugins` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/dashboard/plugins/rescan
`harness/cli/web_server.py` declares `GET /api/dashboard/plugins/rescan` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/dashboard/themes
`harness/cli/web_server.py` declares `GET /api/dashboard/themes` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/env
`harness/cli/web_server.py` declares `GET /api/env` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/logs
`harness/cli/web_server.py` declares `GET /api/logs` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/model/info
`harness/cli/web_server.py` declares `GET /api/model/info` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/providers/oauth
`harness/cli/web_server.py` declares `GET /api/providers/oauth` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/providers/oauth/{provider_id}/poll/{session_id}
`harness/cli/web_server.py` declares `GET /api/providers/oauth/{provider_id}/poll/{session_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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/sessions
`harness/cli/web_server.py` declares `GET /api/sessions` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/sessions/search
`harness/cli/web_server.py` declares `GET /api/sessions/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 /api/sessions/{session_id}
`harness/cli/web_server.py` declares `GET /api/sessions/{session_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/sessions/{session_id}/messages
`harness/cli/web_server.py` declares `GET /api/sessions/{session_id}/messages` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/skills
`harness/cli/web_server.py` declares `GET /api/skills` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/status
`harness/cli/web_server.py` declares `GET /api/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/tools/toolsets
`harness/cli/web_server.py` declares `GET /api/tools/toolsets` 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-plugins/{plugin_name}/{file_path:path}
`harness/cli/web_server.py` declares `GET /dashboard-plugins/{plugin_name}/{file_path:path}` 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 wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /messages
`scripts/whatsapp-bridge/bridge.js` declares `GET /messages` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{full_path:path}
`harness/cli/web_server.py` declares `GET /{full_path:path}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/cron/jobs
`harness/cli/web_server.py` declares `POST /api/cron/jobs` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/cron/jobs/{job_id}/pause
`harness/cli/web_server.py` declares `POST /api/cron/jobs/{job_id}/pause` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/cron/jobs/{job_id}/resume
`harness/cli/web_server.py` declares `POST /api/cron/jobs/{job_id}/resume` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/cron/jobs/{job_id}/trigger
`harness/cli/web_server.py` declares `POST /api/cron/jobs/{job_id}/trigger` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/env/reveal
`harness/cli/web_server.py` declares `POST /api/env/reveal` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/gateway/restart
`harness/cli/web_server.py` declares `POST /api/gateway/restart` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/hermes/update
`harness/cli/web_server.py` declares `POST /api/hermes/update` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/providers/oauth/{provider_id}/start
`harness/cli/web_server.py` declares `POST /api/providers/oauth/{provider_id}/start` 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 /api/providers/oauth/{provider_id}/submit
`harness/cli/web_server.py` declares `POST /api/providers/oauth/{provider_id}/submit` 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 /edit
`scripts/whatsapp-bridge/bridge.js` declares `POST /edit` 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 /send
`scripts/whatsapp-bridge/bridge.js` declares `POST /send` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /send-media
`scripts/whatsapp-bridge/bridge.js` declares `POST /send-media` 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 /typing
`scripts/whatsapp-bridge/bridge.js` declares `POST /typing` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /api/config
`harness/cli/web_server.py` declares `PUT /api/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: PUT /api/config/raw
`harness/cli/web_server.py` declares `PUT /api/config/raw` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /api/cron/jobs/{job_id}
`harness/cli/web_server.py` declares `PUT /api/cron/jobs/{job_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: PUT /api/dashboard/theme
`harness/cli/web_server.py` declares `PUT /api/dashboard/theme` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /api/env
`harness/cli/web_server.py` declares `PUT /api/env` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /api/skills/toggle
`harness/cli/web_server.py` declares `PUT /api/skills/toggle` 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: harness/agent/anthropic_adapter.py (1601 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/agent/auxiliary_client.py (3109 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/agent/context_compressor.py (1284 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/agent/credential_pool.py (1348 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/cli/auth.py (3513 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/cli/commands.py (1419 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/cli/config.py (4033 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/cli/doctor.py (1170 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/cli/gateway.py (3210 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/cli/main.py (8899 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/cli/model_switch.py (1377 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/cli/models.py (2726 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/cli/setup.py (3508 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/cli/skills_hub.py (1384 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/cli/tools_config.py (2103 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/cli/web_server.py (2832 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/cron/scheduler.py (1576 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/gateway/platforms/api_server.py (2613 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/gateway/platforms/base.py (2701 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/gateway/platforms/discord.py (3931 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/gateway/platforms/slack.py (1744 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/gateway/platforms/telegram.py (3295 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/gateway/run.py (11361 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/gateway/session.py (1277 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/repl.py (11094 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/run_agent.py (12000 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/state.py (1607 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/tools/browser_tool.py (2514 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/tools/code_execution_tool.py (1579 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/tools/delegate_tool.py (2168 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/tools/file_operations.py (1251 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/tools/mcp_tool.py (2681 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/tools/skills_hub.py (3054 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/tools/skills_tool.py (1445 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/tools/terminal_tool.py (2076 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/tools/tts_tool.py (1515 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: harness/tools/web_tools.py (2101 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: scripts/install.sh (1436 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/agent/test_anthropic_adapter.py (1749 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/agent/test_auxiliary_client.py (1205 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/agent/test_bedrock_adapter.py (1232 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/cli/test_auth_commands.py (1476 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/cli/test_commands.py (1326 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/cli/test_gateway_service.py (1987 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/cli/test_runtime_provider_resolution.py (1501 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/cli/test_update_gateway_restart.py (1263 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/cli/test_web_server.py (1672 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/cron/test_scheduler.py (1746 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/gateway/test_api_server.py (2184 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/gateway/test_slack.py (1923 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/gateway/test_stream_consumer.py (1334 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/gateway/test_voice_command.py (2708 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/run_agent/test_run_agent.py (4682 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/run_agent/test_streaming.py (1357 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_state.py (1914 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/tools/test_delegate.py (2026 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/tools/test_mcp_tool.py (3152 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/tools/test_send_message_tool.py (1326 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/tools/test_skills_hub.py (1361 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/tools/test_tirith_security.py (998 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/tools/test_transcription_tools.py (1256 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/tools/test_voice_cli_integration.py (1296 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/0f54f343-b0d6-4b10-87cd-63f4c1eeff4b/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/0f54f343-b0d6-4b10-87cd-63f4c1eeff4b/

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.