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

zhiro-labs/dango

https://github.com/zhiro-labs/dango · scanned 2026-06-16 01:12 UTC (2 months, 1 week ago)

93 raw signals (0 security + 93 graph)

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

Complete repo analysis

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

JSON
Combined
64.7
/100
Security checks
65
0 findings
System graph
65
100.0% cov · 91 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 28 Medium 5 Low 55 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 91 Crowd 0 Layer: Software 8 Hardware 3 Frontend 1 Security 29 Cicd 4 Quality 8 Api 38
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 64.7/100 with 100.0% coverage. It contains 372 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 93 findings — concentrated in api (38), security (29), software (8). Risk profile is high: 0 critical, 28 high, 7 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 88 of 91 actionable findings. 93 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 `add_custom_api` without auth dependency — web/main.py:642
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:642 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `add_runtime_channel` without auth dependency — web/main.py:535
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:535 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `add_runtime_user` without auth dependency — web/main.py:557
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:557 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `add_sql_database` without auth dependency — web/main.py:680
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:680 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `bot_restart` without auth dependency — web/main.py:308
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:308 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `bot_start` without auth dependency — web/main.py:290
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:290 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `bot_stop` without auth dependency — web/main.py:299
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:299 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `clear_logs` without auth dependency — web/main.py:220
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:220 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `delete_custom_api` without auth dependency — web/main.py:661
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:661 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `delete_runtime_channel` without auth dependency — web/main.py:548
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:548 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `delete_runtime_user` without auth dependency — web/main.py:570
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:570 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `delete_sql_database` without auth dependency — web/main.py:697
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:697 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `save_advanced` without auth dependency — web/main.py:492
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:492 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `save_apis_enable` without auth dependency — web/main.py:634
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:634 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `save_dbs_enable` without auth dependency — web/main.py:672
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:672 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `save_deep_model` without auth dependency — web/main.py:416
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:416 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `save_discord` without auth dependency — web/main.py:392
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:392 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `save_fast_model` without auth dependency — web/main.py:401
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:401 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `save_features` without auth dependency — web/main.py:431
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:431 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `save_google_settings` without auth dependency — web/main.py:454
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:454 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `save_prompt` without auth dependency — web/main.py:384
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:384 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `save_runtime_settings` without auth dependency — web/main.py:518
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:518 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `save_workspace_prompt` without auth dependency — web/main.py:579
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:579 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `save_workspace` without auth dependency — web/main.py:506
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:506 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `setup_complete` without auth dependency — web/main.py:136
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:136 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `shutdown_all` without auth dependency — web/main.py:317
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:317 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `validate_discord` without auth dependency — web/main.py:339
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:339 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `validate_google` without auth dependency — web/main.py:358
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
web/main.py:358 securityAuth fastapi unauth mutation
medium System graph hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned
docker/login-action@v3 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 24, 31, 34
.github/workflows/docker.yml:24, 31, 34 (3 hits)
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/docker.yml CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/docs.yml CI/CD securitySupply chainGithub actions
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
low System graph quality Integrity conf 1.00 10 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `COMPOSE_PROJECT_NAME`, `DATA_DIR`, `DEEP_BASE_URL`, `DOCKER_SOCKET`, `ENABLE_CUSTOM_APIS`, `ENABLE_SQL_DATABASES`, `FAST_BASE_URL`, `GEMINI_TEMPERATURE` + 2 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 154 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.12-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:1 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
actions/deploy-pages@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/docs.yml:53 CI/CD securitySupply chainGithub actions
low System graph quality Tests conf 1.00 Low test-to-source ratio
5 tests / 24 src (ratio 0.21).
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 10 places
Functions with the same first-5-line body hash: dango/commands/admin_commands.py:addchannel, dango/commands/admin_commands.py:removechannel, dango/commands/admin_commands.py:listchannels, dango/commands/admin_commands.py:adduser This is *the* AI-coder failure mode (4× more duplication in vibe-code…
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_split_message_legacy` in dango/utils/discord_helpers.py:409
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: crawl_website
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dango/steps/call_agent.py:394
low System graph software Dead code conf 1.00 Possibly dead Python function: isatty
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
main.py:32
low System graph software Dead code conf 1.00 Possibly dead Python function: read_url
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dango/steps/call_agent.py:383
low System graph software Dead code conf 1.00 Possibly dead Python function: reload
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dango/utils/runtime_config.py:225
low System graph software Dead code conf 1.00 Possibly dead Python function: replacer
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dango/steps/fetch_history.py:288
low System graph software Dead code conf 1.00 Possibly dead Python function: set_token_counter
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dango/utils/complexity_router.py:46
low System graph software Dead code conf 1.00 Possibly dead Python function: update_channel_metadata
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dango/utils/runtime_config.py:230
low System graph software Dead code conf 1.00 Possibly dead Python function: update_user_metadata
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
dango/utils/runtime_config.py:239
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`web/main.py` declares `GET /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/bot/status
`web/main.py` declares `GET /api/bot/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/logs
`web/main.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 /dashboard
`web/main.py` declares `GET /dashboard` 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 /discord
`web/main.py` declares `GET /discord` 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 /models
`web/main.py` declares `GET /models` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /overview
`web/main.py` declares `GET /overview` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /prompt
`web/main.py` declares `GET /prompt` 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 /setup
`web/main.py` declares `GET /setup` 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 /tools
`web/main.py` declares `GET /tools` 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/bot/restart
`web/main.py` declares `POST /api/bot/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/bot/start
`web/main.py` declares `POST /api/bot/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 consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/bot/stop
`web/main.py` declares `POST /api/bot/stop` 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/config/advanced
`web/main.py` declares `POST /api/config/advanced` 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/config/discord
`web/main.py` declares `POST /api/config/discord` 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/config/features
`web/main.py` declares `POST /api/config/features` 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/config/google
`web/main.py` declares `POST /api/config/google` 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/config/models/deep
`web/main.py` declares `POST /api/config/models/deep` 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/config/models/fast
`web/main.py` declares `POST /api/config/models/fast` 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/config/prompt
`web/main.py` declares `POST /api/config/prompt` 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/config/tools/api
`web/main.py` declares `POST /api/config/tools/api` 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/config/tools/api/{index}/delete
`web/main.py` declares `POST /api/config/tools/api/{index}/delete` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/config/tools/apis/enable
`web/main.py` declares `POST /api/config/tools/apis/enable` 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/config/tools/db
`web/main.py` declares `POST /api/config/tools/db` 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/config/tools/db/{index}/delete
`web/main.py` declares `POST /api/config/tools/db/{index}/delete` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/config/tools/dbs/enable
`web/main.py` declares `POST /api/config/tools/dbs/enable` 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/config/workspace
`web/main.py` declares `POST /api/config/workspace` 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/logs/clear
`web/main.py` declares `POST /api/logs/clear` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/runtime/channels/add
`web/main.py` declares `POST /api/runtime/channels/add` 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/runtime/channels/{channel_id}/delete
`web/main.py` declares `POST /api/runtime/channels/{channel_id}/delete` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/runtime/settings
`web/main.py` declares `POST /api/runtime/settings` 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/runtime/users/add
`web/main.py` declares `POST /api/runtime/users/add` 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/runtime/users/{user_id}/delete
`web/main.py` declares `POST /api/runtime/users/{user_id}/delete` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/shutdown
`web/main.py` declares `POST /api/shutdown` 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/validate/discord
`web/main.py` declares `POST /api/validate/discord` 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/validate/google
`web/main.py` declares `POST /api/validate/google` 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/workspace-prompt
`web/main.py` declares `POST /api/workspace-prompt` 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 /setup/complete
`web/main.py` declares `POST /setup/complete` 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
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/f243b1e9-93a0-4300-9ad2-8d6991b8c152/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/f243b1e9-93a0-4300-9ad2-8d6991b8c152/

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.