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

RJL667/veilguard

https://github.com/RJL667/veilguard · scanned 2026-06-15 23:52 UTC (2 months, 3 weeks ago)

250 raw signals (0 security + 250 graph)

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

Complete repo analysis

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

JSON
Combined
57.4
/100
Security checks
57
0 findings
System graph
57
100.0% cov · 231 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 32 Medium 20 Low 84 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 231 Crowd 0 Layer: Software 8 Frontend 1 Hardware 7 Security 37 Cicd 1 Quality 127 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 57.4/100 with 100.0% coverage. It contains 4117 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 250 findings — concentrated in quality (146), api (50), security (37). Risk profile is high: 0 critical, 32 high, 20 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 136 of 231 actionable findings. 250 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 `admin_requeue_semantic` without auth dependency — services/tcmm-service/server.py:3324
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/tcmm-service/server.py:3324 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `agent_query` without auth dependency — agent-runtime/app/main.py:2101
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
agent-runtime/app/main.py:2101 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `apr_resume_endpoint` without auth dependency — agent-runtime/app/main.py:2081
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
agent-runtime/app/main.py:2081 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_key` without auth dependency — agent-runtime/app/a2a_external.py:205
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
agent-runtime/app/a2a_external.py:205 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_team_endpoint` without auth dependency — agent-runtime/app/main.py:1255
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
agent-runtime/app/main.py:1255 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `debug_evict` without auth dependency — services/tcmm-service/server.py:3496
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/tcmm-service/server.py:3496 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `delegate_to_org` without auth dependency — agent-runtime/app/main.py:1166
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
agent-runtime/app/main.py:1166 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `documents_snapshot` without auth dependency — agent-runtime/app/main.py:1409
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
agent-runtime/app/main.py:1409 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `external_send_message` without auth dependency — agent-runtime/app/a2a_external.py:275
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
agent-runtime/app/a2a_external.py:275 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `generate_stream` without auth dependency — services/tcmm-service/server.py:2221
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/tcmm-service/server.py:2221 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `generate` without auth dependency — services/tcmm-service/server.py:2096
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/tcmm-service/server.py:2096 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest_text` without auth dependency — services/tcmm-service/server.py:2938
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/tcmm-service/server.py:2938 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ingest_turn` without auth dependency — services/tcmm-service/server.py:2883
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/tcmm-service/server.py:2883 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `lesson_decision` without auth dependency — agent-runtime/app/main.py:1616
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
agent-runtime/app/main.py:1616 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `pin_system_prompt` without auth dependency — services/tcmm-service/server.py:1896
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/tcmm-service/server.py:1896 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `pin_tool_definitions` without auth dependency — services/tcmm-service/server.py:1924
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/tcmm-service/server.py:1924 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `pin_user_profile` without auth dependency — services/tcmm-service/server.py:1996
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/tcmm-service/server.py:1996 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_response` without auth dependency — services/tcmm-service/server.py:2705
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/tcmm-service/server.py:2705 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `pre_request` without auth dependency — services/tcmm-service/server.py:1399
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/tcmm-service/server.py:1399 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `proactive_config_set` without auth dependency — agent-runtime/app/main.py:2016
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
agent-runtime/app/main.py:2016 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `proposal_convert` without auth dependency — agent-runtime/app/main.py:1086
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
agent-runtime/app/main.py:1086 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `proposal_decision` without auth dependency — agent-runtime/app/main.py:1320
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
agent-runtime/app/main.py:1320 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `proposal_emit` without auth dependency — agent-runtime/app/main.py:940
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
agent-runtime/app/main.py:940 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `render_structured` without auth dependency — services/tcmm-service/server.py:2376
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/tcmm-service/server.py:2376 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `render` without auth dependency — services/tcmm-service/server.py:2552
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/tcmm-service/server.py:2552 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `revoke_key` without auth dependency — agent-runtime/app/a2a_external.py:256
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
agent-runtime/app/a2a_external.py:256 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `search_memory_endpoint` without auth dependency — services/tcmm-service/server.py:3015
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/tcmm-service/server.py:3015 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `send_message_to_agent` without auth dependency — agent-runtime/app/a2a.py:112
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
agent-runtime/app/a2a.py:112 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `task_ledger_set` without auth dependency — agent-runtime/app/main.py:1477
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
agent-runtime/app/main.py:1477 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `task_progress_append` without auth dependency — agent-runtime/app/main.py:1506
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
agent-runtime/app/main.py:1506 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `traverse_memory_endpoint` without auth dependency — services/tcmm-service/server.py:3073
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/tcmm-service/server.py:3073 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `trigger_dream` without auth dependency — services/tcmm-service/server.py:3608
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
services/tcmm-service/server.py:3608 securityAuth fastapi unauth mutation
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/settings.json
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/settings.json 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 license, 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 hardware Security conf 1.00 Dockerfile runs as root: agent-proxy/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: agent-runtime/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: services/admin-dashboard/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in services/client-daemon/setup_server.py:268
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
services/client-daemon/setup_server.py:268 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in services/tcmm-service/server.py:851
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
services/tcmm-service/server.py:851 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in services/client-daemon/veilguard_client.py:479
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
services/client-daemon/veilguard_client.py:479 Subprocess shell true
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in services/code-exec/server.py:76
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
services/code-exec/server.py:76 Subprocess shell true
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in services/sub-agents/core/agentic.py:384
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
services/sub-agents/core/agentic.py:384 Subprocess shell true
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — agent-runtime/demo/run_all.py:41
`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/tcmm_latency_summary.py:63
`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 — services/client-daemon/publish_release.py:51
`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 — services/client-daemon/veilguard_client.py:233
`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 — services/sub-agents/core/client_bridge.py:392
`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 — test_heatmap_streaming.py:24
`requests.post(...)` 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 cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 50 placeholder/mock markers across 29 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 191 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ADMIN_COOKIE_NAME`, `ADMIN_HOST`, `ADMIN_PORT`, `AGENT_LEDGER_AUTO_COMPACT`, `AGENT_LEDGER_COMPACT_INTERVAL_S`, `AGENT_RUNTIME_DEFAULT_AGENT`, `AGENT_RUNTIME_ENABLED`, `AGENT_RUNTIME_URL` + 183 more. Add them (with a placeholder/comment) to .env.e…
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. 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 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 839 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.11-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
services/admin-dashboard/Dockerfile:1 containersPinned dependencies
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.
agent-runtime/Dockerfile:1 containersPinned dependencies
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.
agent-proxy/Dockerfile:1 containersPinned dependencies
low System graph quality Integrity conf 1.00 20 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: _dag_harness.py:post, _edge_harness.py:post 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.
20 occurrences
repo-level (20 hits)
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_evict_old` in agent-runtime/app/runtime_health/apr.py:97
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 `_FauxTaskFromLegacy` in services/sub-agents/tools/client_admin.py:148
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 `clipboard_copy` in services/sub-agents/tools/clipboard.py:8
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 `clipboard_copy` in services/sub-agents/tools/tool_search.py:49
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 `clipboard_copy` in services/sub-agents/utils/safety.py:14
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_eligible_basic_done_task_45d_old` in agent-runtime/app/proposals/tests/test_outcomes.py:147
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: cmd_record
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/perf_audit.py:70
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_summary
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/perf_audit.py:111
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_tail
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
scripts/perf_audit.py:99
low System graph software Dead code conf 1.00 Possibly dead Python function: fire_now
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent-runtime/app/proposals/dream_scanner.py:303
low System graph software Dead code conf 1.00 Possibly dead Python function: notify_importance
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent-runtime/app/proposals/dream_scanner.py:286
low System graph software Dead code conf 1.00 Possibly dead Python function: sort_key
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent-runtime/app/runtime_health/revision_lane.py:59
low System graph software Dead code conf 1.00 Possibly dead Python function: subscriber_count
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent-runtime/app/events.py:147
low System graph software Dead code conf 1.00 Possibly dead Python function: write_lesson
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
agent-runtime/app/proposals/lessons.py:159
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 quality Integrity conf 1.00 Stub function `create_sdk_mcp_server` (body is just `pass`/`return`) — agent-runtime/app/tools/ledger_mcp.py:64
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 `create_sdk_mcp_server` (body is just `pass`/`return`) — agent-runtime/app/tools/memory_mcp.py:56
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 /agents
`agent-runtime/app/main.py` declares `GET /agents` 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 /agents/{agent_id}/inbox
`agent-runtime/app/a2a.py` declares `GET /agents/{agent_id}/inbox` 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 /agents/{agent_id}/tasks/{task_id}
`agent-runtime/app/a2a.py` declares `GET /agents/{agent_id}/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 /apr/status
`agent-runtime/app/main.py` declares `GET /apr/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 /audit/tcmm_source_kinds
`agent-runtime/app/main.py` declares `GET /audit/tcmm_source_kinds` 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 /constitution
`agent-runtime/app/main.py` declares `GET /constitution` 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 /documents/authority
`agent-runtime/app/main.py` declares `GET /documents/authority` 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 /documents/history
`agent-runtime/app/main.py` declares `GET /documents/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 /events
`agent-runtime/app/main.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: GET /lessons/amendment_candidates
`agent-runtime/app/main.py` declares `GET /lessons/amendment_candidates` 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 /lessons/review_queue
`agent-runtime/app/main.py` declares `GET /lessons/review_queue` 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 /memory_status
`services/tcmm-service/server.py` declares `GET /memory_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 /proactive_config
`agent-runtime/app/main.py` declares `GET /proactive_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 /proposals
`agent-runtime/app/main.py` declares `GET /proposals` 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 /proposals/{proposal_id}
`agent-runtime/app/main.py` declares `GET /proposals/{proposal_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /replay/{task_id}
`agent-runtime/app/main.py` declares `GET /replay/{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 /tasks/{task_id}
`agent-runtime/app/main.py` declares `GET /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 /tasks/{task_id}/ledger
`agent-runtime/app/main.py` declares `GET /tasks/{task_id}/ledger` 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 /teams
`agent-runtime/app/main.py` declares `GET /teams` 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 /teams/{team_id}/cost
`agent-runtime/app/main.py` declares `GET /teams/{team_id}/cost` 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 /tool_invocations
`services/tcmm-service/server.py` declares `GET /tool_invocations` 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 /tool_invocations/{tool_name}
`services/tcmm-service/server.py` declares `GET /tool_invocations/{tool_name}` 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 /tool_pairs
`services/tcmm-service/server.py` declares `GET /tool_pairs` 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 /work_items
`agent-runtime/app/main.py` declares `GET /work_items` 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 /workspace/file
`agent-runtime/app/main.py` declares `GET /workspace/file` 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 /agent/query
`agent-runtime/app/main.py` declares `POST /agent/query` 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 /agents/{agent_id}/messages
`agent-runtime/app/a2a.py` declares `POST /agents/{agent_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: POST /apr/resume
`agent-runtime/app/main.py` declares `POST /apr/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 /delegate
`agent-runtime/app/main.py` declares `POST /delegate` 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 /documents/snapshot
`agent-runtime/app/main.py` declares `POST /documents/snapshot` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /generate
`services/tcmm-service/server.py` declares `POST /generate` 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 /generate_stream
`services/tcmm-service/server.py` declares `POST /generate_stream` 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 /ingest_turn
`services/tcmm-service/server.py` declares `POST /ingest_turn` 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 /keys
`agent-runtime/app/a2a_external.py` declares `POST /keys` 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 /keys/{key_id}/revoke
`agent-runtime/app/a2a_external.py` declares `POST /keys/{key_id}/revoke` 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 /lessons/{lesson_id}/decision
`agent-runtime/app/main.py` declares `POST /lessons/{lesson_id}/decision` 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 /pin/system_prompt
`services/tcmm-service/server.py` declares `POST /pin/system_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 /pin/tool_definitions
`services/tcmm-service/server.py` declares `POST /pin/tool_definitions` 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 /pin/user_profile
`services/tcmm-service/server.py` declares `POST /pin/user_profile` 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 /post_response
`services/tcmm-service/server.py` declares `POST /post_response` 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 /pre_request
`services/tcmm-service/server.py` declares `POST /pre_request` 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 /proactive_config
`agent-runtime/app/main.py` declares `POST /proactive_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: POST /proposals/emit
`agent-runtime/app/main.py` declares `POST /proposals/emit` 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 /proposals/{proposal_id}/convert
`agent-runtime/app/main.py` declares `POST /proposals/{proposal_id}/convert` 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 /proposals/{proposal_id}/decision
`agent-runtime/app/main.py` declares `POST /proposals/{proposal_id}/decision` 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 /render
`services/tcmm-service/server.py` declares `POST /render` 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 /render_structured
`services/tcmm-service/server.py` declares `POST /render_structured` 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 /tasks/{task_id}/ledger
`agent-runtime/app/main.py` declares `POST /tasks/{task_id}/ledger` 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 /tasks/{task_id}/progress
`agent-runtime/app/main.py` declares `POST /tasks/{task_id}/progress` 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 /teams
`agent-runtime/app/main.py` declares `POST /teams` 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: agent-proxy/app/main.py (5932 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: agent-runtime/app/main.py (2223 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: agent-runtime/app/tools/ledger_mcp.py (1469 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: agent-runtime/app/workers/inbox_poller.py (1566 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: agent/base.py (1135 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: services/client-daemon/daemon/tray.py (1388 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: services/client-daemon/veilguard_client.py (2031 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: services/tcmm-service/server.py (3811 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/47e7f1b2-ace2-474a-a547-f015328af58e/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/47e7f1b2-ace2-474a-a547-f015328af58e/

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.