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

Daniele122898/agent-graphs

https://github.com/Daniele122898/agent-graphs · scanned 2026-06-17 01:25 UTC (1 month, 2 weeks ago)

79 raw signals (0 security + 79 graph)

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

Complete repo analysis

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

JSON
Combined
70.3
/100
Security checks
70
0 findings
System graph
70
77.8% cov · 76 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 17 Medium 16 Low 34 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 76 Crowd 0 Layer: Software 9 Frontend 1 Security 18 Quality 28 Api 20
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 70.3/100 with 77.8% coverage. It contains 956 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 79 findings — concentrated in quality (31), api (20), security (18). Risk profile is high: 0 critical, 17 high, 16 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 63 of 76 actionable findings. 79 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 `answer_question` without auth dependency — backend/api/questions.py:19
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/questions.py:19 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `clear_agent_history` without auth dependency — backend/api/agents.py:49
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/agents.py:49 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_task` without auth dependency — backend/api/tasks.py:27
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/tasks.py:27 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_team` without auth dependency — backend/api/teams.py:18
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/teams.py:18 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `install` without auth dependency — backend/api/internal.py:23
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/internal.py:23 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `interject_agent` without auth dependency — backend/api/agents.py:28
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/agents.py:28 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `launch_session` without auth dependency — backend/api/sessions.py:22
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/sessions.py:22 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `rename_team` without auth dependency — backend/api/teams.py:46
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/teams.py:46 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `resume_session` without auth dependency — backend/api/sessions.py:43
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/sessions.py:43 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `retry_task` without auth dependency — backend/api/tasks.py:50
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/tasks.py:50 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `run_agent` without auth dependency — backend/api/agents.py:20
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/agents.py:20 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `set_mode` without auth dependency — backend/api/sessions.py:64
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/sessions.py:64 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `stop_agent` without auth dependency — backend/api/agents.py:73
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/agents.py:73 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `summarize_agent_history` without auth dependency — backend/api/agents.py:59
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/agents.py:59 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `put_team_graph` without auth dependency — backend/api/teams.py:42
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/api/teams.py:42 securityAuth fastapi unauth mutation
high System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in backend/agents/tools.py:131
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
backend/agents/tools.py:131 Subprocess shell true
high System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in backend/runtime/tasks.py:176
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
backend/runtime/tasks.py:176 Subprocess shell true
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — backend/harness/opencode/tools/ask_agent.ts:21
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/lib/api.ts:48
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 authority lacks a verifier contract: backend/agents/CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
backend/agents/CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: backend/api/CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
backend/api/CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: backend/CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
backend/CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: backend/runtime/CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
backend/runtime/CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
CLAUDE.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: frontend/CLAUDE.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
frontend/CLAUDE.md VerificationClaude instruction
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 ci. 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 Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — backend/agents/tools.py:131
`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 — backend/runtime/tasks.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 — scripts/verify_ui.py:223
`urllib.request.urlopen(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 14 placeholder/mock markers across 10 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 18 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 4 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/providers/lmstudio.py:build_lmstudio_model, backend/providers/lmstudio.py:build 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.
4 occurrences
repo-level (4 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `model_copy` in backend/runtime/workers.py:63
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: agent_info
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/harness/opencode/client.py:68
low System graph software Dead code conf 1.00 Possibly dead Python function: all_completed
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/agents/todos.py:48
low System graph software Dead code conf 1.00 Possibly dead Python function: all_lifecycles
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/runtime/sessions.py:74
low System graph software Dead code conf 1.00 Possibly dead Python function: processor
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/agents/history.py:52
low System graph software Dead code conf 1.00 Possibly dead Python function: run_agent
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend/wiring.py:94
low System graph software Dead code conf 1.00 Possibly dead Python function: scripted_model
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/scripted_backend.py:30
low System graph frontend Frontend quality conf 1.00 React Flow edge with `label=` but no project-wide edge-label CSS override — frontend/src/canvas/graphMapping.ts:24
React Flow edge labels render with a white rectangle behind the text by default, which scatters bright boxes across a dark canvas. Either drop the label, or override `.react-flow__edge-textbg` and `.react-flow__edge-text` in your stylesheet. Why: P-H in CHECKLIST.md — vendor edge labels bleed whit…
Fq edge label no bg
low System graph quality Integrity conf 1.00 Stub function `log_message` (body is just `pass`/`return`) — specs/opencode-smoke/stub.py:24
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: GET /api/agent/{agent_id}/history
`backend/api/agents.py` declares `GET /api/agent/{agent_id}/history` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/messages
`backend/api/agents.py` declares `GET /api/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/questions
`backend/api/questions.py` declares `GET /api/questions` 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/session
`backend/api/sessions.py` declares `GET /api/session` 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/stats/usage/{agent_id}
`backend/api/stats.py` declares `GET /api/stats/usage/{agent_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/tasks
`backend/api/tasks.py` declares `GET /api/tasks` 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/tasks/{task_id}
`backend/api/tasks.py` declares `GET /api/tasks/{task_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/teams/{team_id}
`backend/api/teams.py` declares `GET /api/teams/{team_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 /events
`backend/api/agents.py` declares `GET /events` 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/agent/{agent_id}/history/clear
`backend/api/agents.py` declares `POST /api/agent/{agent_id}/history/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/agent/{agent_id}/history/summarize
`backend/api/agents.py` declares `POST /api/agent/{agent_id}/history/summarize` 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/agent/{agent_id}/interject
`backend/api/agents.py` declares `POST /api/agent/{agent_id}/interject` 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/agent/{agent_id}/run
`backend/api/agents.py` declares `POST /api/agent/{agent_id}/run` 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/agent/{agent_id}/stop
`backend/api/agents.py` declares `POST /api/agent/{agent_id}/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/questions/{question_id}/answer
`backend/api/questions.py` declares `POST /api/questions/{question_id}/answer` 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/session/mode
`backend/api/sessions.py` declares `POST /api/session/mode` 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/sessions/{session_id}/resume
`backend/api/sessions.py` declares `POST /api/sessions/{session_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/tasks
`backend/api/tasks.py` declares `POST /api/tasks` 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/teams/{team_id}/rename
`backend/api/teams.py` declares `POST /api/teams/{team_id}/rename` 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 /internal/ask_agent
`backend/api/internal.py` declares `POST /internal/ask_agent` 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/a0448129-4716-4956-8823-5fbf294547bf/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/a0448129-4716-4956-8823-5fbf294547bf/

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.