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

csilvasantin/32.-ConsejoAdmiraNextGame

https://github.com/csilvasantin/32.-ConsejoAdmiraNextGame · scanned 2026-06-17 01:51 UTC (1 month, 1 week ago)

96 raw signals (0 security + 96 graph)

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

Complete repo analysis

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

JSON
Combined
64.9
/100
Security checks
65
0 findings
System graph
65
88.9% cov · 92 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 12 Medium 30 Low 49 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 92 Crowd 0 Layer: Software 2 Frontend 1 Security 24 Cicd 2 Quality 19 Api 44
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.9/100 with 88.9% coverage. It contains 763 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 96 findings — concentrated in api (44), security (24), quality (20). Risk profile is high: 0 critical, 12 high, 30 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 91 of 92 actionable findings. 96 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 yar_create_task` — council-api.py:1756
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…
council-api.py:1756 Sync io in asyncPerformance
high System graph quality Integrity conf 1.00 Blocking `time.sleep(...)` inside `async def yar_projects` — council-api.py:1845
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…
council-api.py:1845 Sync io in asyncPerformance
high System graph quality Integrity conf 1.00 Blocking `time.sleep(...)` inside `async def yar_task_action` — council-api.py:1666
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…
council-api.py:1666 Sync io in asyncPerformance
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/machines (public/app.js:391)
`public/app.js:391` calls `GET /api/machines` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/machines` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/machines (public/new-member.js:773)
`public/new-member.js:773` calls `GET /api/machines` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/machines` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/machines (public/new-member.js:814)
`public/new-member.js:814` calls `POST /api/machines` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/machines` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/machines/${id}/sync (docs/app.js:241)
`docs/app.js:241` calls `POST /api/machines/${id}/sync` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/machines/<p>/sync` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/machines/${id}/sync (public/app.js:241)
`public/app.js:241` calls `POST /api/machines/${id}/sync` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/machines/<p>/sync` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://catbox.moe/user/api.php (tools/chatgpt-crear-worker.mjs:249)
`tools/chatgpt-crear-worker.mjs:249` calls `POST https://catbox.moe/user/api.php` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/catbox.moe/user/api.php` If this points at an external API, prefix it with `htt…
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI POST `council_import_to_stock` without auth dependency — council-api.py:2664
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
council-api.py:2664 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `council_presentar` without auth dependency — council-api.py:2757
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
council-api.py:2757 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `tube_import_to_stock` without auth dependency — council-api.py:2657
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
council-api.py:2657 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — docs/app.js:241
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — public/app.js:241
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — public/new-member.js:783
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — tools/chatgpt-crear-worker.mjs:227
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — tools/yarig-tasks-sync.mjs:69
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, tests. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Tests conf 1.00 CI is configured but no tests are detected
A CI pipeline exists, but the scan found no test files to gate. Opus labeled this generated-code pattern as config theater: release machinery exists, but it has little behavioral signal.
CI/CDConfig theaterRepo hardening
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/pages.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in src/server.js:34
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
src/server.js:34 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in council-scumm.html:2971
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
council-scumm.html:2971 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in dashboard.html:149
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
dashboard.html:149 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/app.js:227
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/app.js:227 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/teamwork.js:98
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/teamwork.js:98 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/app.js:227
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/app.js:227 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/council-scumm.html:2760
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/council-scumm.html:2760 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/dashboard.html:149
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/dashboard.html:149 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/game.html:822
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/game.html:822 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/teamwork.js:98
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/teamwork.js:98 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in subasta.html:165
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
subasta.html:165 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in teamwork.js:98
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
teamwork.js:98 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_outerhtml_assignment' in docs/teamwork.js:1110
Found a known-risky pattern (direct_outerhtml_assignment). Review and replace if possible.
docs/teamwork.js:1110 Direct outerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_outerhtml_assignment' in public/teamwork.js:1110
Found a known-risky pattern (direct_outerhtml_assignment). Review and replace if possible.
public/teamwork.js:1110 Direct outerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_outerhtml_assignment' in teamwork.js:1110
Found a known-risky pattern (direct_outerhtml_assignment). Review and replace if possible.
teamwork.js:1110 Direct outerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in docs/teamwork.js:1111
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
docs/teamwork.js:1111 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in public/teamwork.js:1111
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
public/teamwork.js:1111 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in teamwork.js:1111
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
teamwork.js:1111 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/server.js:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/server.js:4 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/ssh-exec.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/ssh-exec.js:1 Node child process
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 14 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, tests. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 30 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph cicd CI/CD security conf 1.00 4 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 26, 67, 70, 76
.github/workflows/pages.yml:26, 67, 70, 76 (4 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: council-api.py:agent_ask_anthropic, council-api.py:agent_ask This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: council-api.py:yar_projects, council-api.py:prepare_yar_login_session, council-api.py:yar_logout_session This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why th…
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph software Dead code conf 1.00 Possibly dead Python function: daily_generate
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
council-api.py:3121
low System graph software Dead code conf 1.00 Possibly dead Python function: verify_token
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
council-api.py:743
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/server.js:780
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`council-api.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/council/budget
`council-api.py` declares `GET /api/council/budget` 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/council/crear-pending
`council-api.py` declares `GET /api/council/crear-pending` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/council/crear/{job_id}
`council-api.py` declares `GET /api/council/crear/{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/council/daily
`council-api.py` declares `GET /api/council/daily` 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/council/diario
`council-api.py` declares `GET /api/council/diario` 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/council/entrenar/{gen}
`council-api.py` declares `GET /api/council/entrenar/{gen}` 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/council/entrenar/{gen}/{persona}
`council-api.py` declares `GET /api/council/entrenar/{gen}/{persona}` 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/council/health
`council-api.py` declares `GET /api/council/health` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/council/importar-video/{job_id}
`council-api.py` declares `GET /api/council/importar-video/{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/council/models
`council-api.py` declares `GET /api/council/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 /api/council/presentation
`council-api.py` declares `GET /api/council/presentation` 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/council/yar-context
`council-api.py` declares `GET /api/council/yar-context` 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/council/yar-status
`council-api.py` declares `GET /api/council/yar-status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/council/analyze-youtube
`council-api.py` declares `POST /api/council/analyze-youtube` 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/council/ask
`council-api.py` declares `POST /api/council/ask` 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/council/ask-one
`council-api.py` declares `POST /api/council/ask-one` 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/council/crear
`council-api.py` declares `POST /api/council/crear` 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/council/crear/claim
`council-api.py` declares `POST /api/council/crear/claim` 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/council/crear/{job_id}/error
`council-api.py` declares `POST /api/council/crear/{job_id}/error` 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/council/crear/{job_id}/result
`council-api.py` declares `POST /api/council/crear/{job_id}/result` 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/council/diario/append
`council-api.py` declares `POST /api/council/diario/append` 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/council/entrenar/{gen}/{persona}/merge
`council-api.py` declares `POST /api/council/entrenar/{gen}/{persona}/merge` 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/council/hackeo
`council-api.py` declares `POST /api/council/hackeo` 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/council/hackeo/discover-macs
`council-api.py` declares `POST /api/council/hackeo/discover-macs` 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/council/hackeo/stop
`council-api.py` declares `POST /api/council/hackeo/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/council/import-to-stock
`council-api.py` declares `POST /api/council/import-to-stock` 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/council/importar-video
`council-api.py` declares `POST /api/council/importar-video` 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/council/leer
`council-api.py` declares `POST /api/council/leer` 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/council/presentar
`council-api.py` declares `POST /api/council/presentar` 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/council/yar-context
`council-api.py` declares `POST /api/council/yar-context` 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/council/yar-create-task
`council-api.py` declares `POST /api/council/yar-create-task` 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/council/yar-login
`council-api.py` declares `POST /api/council/yar-login` 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/council/yar-logout
`council-api.py` declares `POST /api/council/yar-logout` 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/council/yar-projects
`council-api.py` declares `POST /api/council/yar-projects` 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/council/yar-sync
`council-api.py` declares `POST /api/council/yar-sync` 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/council/yar-task-action
`council-api.py` declares `POST /api/council/yar-task-action` 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 /tube/import-to-stock
`council-api.py` declares `POST /tube/import-to-stock` 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: council-api.py (3863 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/ssh-exec.js (2012 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/95fec80e-367b-4dae-8375-86fef2d2d01c/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/95fec80e-367b-4dae-8375-86fef2d2d01c/

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.