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

saltbo/any-managed-agents

https://github.com/saltbo/any-managed-agents · scanned 2026-06-16 00:00 UTC (2 months, 3 weeks ago)

249 raw signals (0 security + 249 graph)

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

Complete repo analysis

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

JSON
Combined
53.4
/100
Security checks
53
0 findings
System graph
53
100.0% cov · 248 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 50 Medium 61 Low 66 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 248 Crowd 0 Layer: Frontend 18 Hardware 3 Security 14 Cicd 1 Quality 115 Api 97
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 53.4/100 with 100.0% coverage. It contains 2666 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 249 findings — concentrated in quality (116), api (97), frontend (18). Risk profile is high: 0 critical, 50 high, 62 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 172 of 248 actionable findings. 249 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 api Wiring conf 1.00 Dangling fetch: DELETE https://example.com/api/v1/auth/sessions/current (server/integration/auth.test.ts:123)
`server/integration/auth.test.ts:123` calls `DELETE https://example.com/api/v1/auth/sessions/current` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/api/v1/auth/sessions/current` If this points at…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com${path} (server/integration/access-rules.test.ts:6)
`server/integration/access-rules.test.ts:6` calls `GET https://example.com${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/<p>` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com${path} (server/integration/agents.test.ts:6)
`server/integration/agents.test.ts:6` calls `GET https://example.com${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/<p>` If this points at an external API, prefix it with `https://` so the…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com${path} (server/integration/audit-records.test.ts:6)
`server/integration/audit-records.test.ts:6` calls `GET https://example.com${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/<p>` If this points at an external API, prefix it with `https://`…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com${path} (server/integration/auth.test.ts:10)
`server/integration/auth.test.ts:10` calls `GET https://example.com${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/<p>` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com${path} (server/integration/budgets.test.ts:6)
`server/integration/budgets.test.ts:6` calls `GET https://example.com${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/<p>` If this points at an external API, prefix it with `https://` so th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com${path} (server/integration/connections.test.ts:6)
`server/integration/connections.test.ts:6` calls `GET https://example.com${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/<p>` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com${path} (server/integration/connectors.test.ts:6)
`server/integration/connectors.test.ts:6` calls `GET https://example.com${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/<p>` If this points at an external API, prefix it with `https://` so…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com${path} (server/integration/effective-policy.test.ts:8)
`server/integration/effective-policy.test.ts:8` calls `GET https://example.com${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/<p>` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com${path} (server/integration/environments.test.ts:6)
`server/integration/environments.test.ts:6` calls `GET https://example.com${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/<p>` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com${path} (server/integration/federated-tenants.test.ts:6)
`server/integration/federated-tenants.test.ts:6` calls `GET https://example.com${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/<p>` If this points at an external API, prefix it with `https…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com${path} (server/integration/leases.test.ts:10)
`server/integration/leases.test.ts:10` calls `GET https://example.com${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/<p>` If this points at an external API, prefix it with `https://` so th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com${path} (server/integration/policies.test.ts:6)
`server/integration/policies.test.ts:6` calls `GET https://example.com${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/<p>` If this points at an external API, prefix it with `https://` so t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com${path} (server/integration/providers-governance.test.ts:6)
`server/integration/providers-governance.test.ts:6` calls `GET https://example.com${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/<p>` If this points at an external API, prefix it with `ht…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com${path} (server/integration/providers.test.ts:10)
`server/integration/providers.test.ts:10` calls `GET https://example.com${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/<p>` If this points at an external API, prefix it with `https://` so…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com${path} (server/integration/restish-openapi.test.ts:17)
`server/integration/restish-openapi.test.ts:17` calls `GET https://example.com${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/<p>` If this points at an external API, prefix it with `https:…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com${path} (server/integration/runners.test.ts:9)
`server/integration/runners.test.ts:9` calls `GET https://example.com${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/<p>` If this points at an external API, prefix it with `https://` so th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com${path} (server/integration/runtimes.test.ts:6)
`server/integration/runtimes.test.ts:6` calls `GET https://example.com${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/<p>` If this points at an external API, prefix it with `https://` so t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com${path} (server/integration/sessions.test.ts:11)
`server/integration/sessions.test.ts:11` calls `GET https://example.com${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/<p>` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com${path} (server/integration/triggers.test.ts:6)
`server/integration/triggers.test.ts:6` calls `GET https://example.com${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/<p>` If this points at an external API, prefix it with `https://` so t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com${path} (server/integration/usage-records.test.ts:10)
`server/integration/usage-records.test.ts:10` calls `GET https://example.com${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/<p>` If this points at an external API, prefix it with `https://…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com${path} (server/integration/usage-summary.test.ts:10)
`server/integration/usage-summary.test.ts:10` calls `GET https://example.com${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/<p>` If this points at an external API, prefix it with `https://…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com${path} (server/integration/vaults.test.ts:7)
`server/integration/vaults.test.ts:7` calls `GET https://example.com${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/<p>` If this points at an external API, prefix it with `https://` so the…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com${path} (server/integration/work-items.test.ts:9)
`server/integration/work-items.test.ts:9` calls `GET https://example.com${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/<p>` If this points at an external API, prefix it with `https://` so…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com/api/v1/auth/config (server/integration/auth.test.ts:30)
`server/integration/auth.test.ts:30` calls `GET https://example.com/api/v1/auth/config` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/api/v1/auth/config` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com/api/v1/auth/config?organization=example-org (server/integration/auth.test.ts:38)
`server/integration/auth.test.ts:38` calls `GET https://example.com/api/v1/auth/config?organization=example-org` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/api/v1/auth/config` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com/api/v1/connectors (server/integration/connectors.test.ts:110)
`server/integration/connectors.test.ts:110` calls `GET https://example.com/api/v1/connectors` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/api/v1/connectors` If this points at an external API, p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com/api/v1/docs (server/integration/openapi.test.ts:449)
`server/integration/openapi.test.ts:449` calls `GET https://example.com/api/v1/docs` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/api/v1/docs` If this points at an external API, prefix it with `…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com/api/v1/health (server/integration/health.test.ts:7)
`server/integration/health.test.ts:7` calls `GET https://example.com/api/v1/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/api/v1/health` If this points at an external API, prefix it with …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com/api/v1/leases/${lease.id}/channel (server/integration/leases.test.ts:491)
`server/integration/leases.test.ts:491` calls `GET https://example.com/api/v1/leases/${lease.id}/channel` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/api/v1/leases/<p>/channel` If this points a…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com/api/v1/leases/${leaseId}/channel (server/integration/leases.test.ts:129)
`server/integration/leases.test.ts:129` calls `GET https://example.com/api/v1/leases/${leaseId}/channel` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/api/v1/leases/<p>/channel` If this points at…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com/api/v1/leases/lease_missing/channel (server/integration/leases.test.ts:480)
`server/integration/leases.test.ts:480` calls `GET https://example.com/api/v1/leases/lease_missing/channel` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/api/v1/leases/lease_missing/channel` If t…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com/api/v1/openapi.json (server/integration/openapi.test.ts:46)
`server/integration/openapi.test.ts:46` calls `GET https://example.com/api/v1/openapi.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/api/v1/openapi.json` If this points at an external API, p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com/api/v1/openapi.json (server/integration/restish-openapi.test.ts:28)
`server/integration/restish-openapi.test.ts:28` calls `GET https://example.com/api/v1/openapi.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/api/v1/openapi.json` If this points at an externa…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com/api/v1/runners (server/integration/runners.test.ts:276)
`server/integration/runners.test.ts:276` calls `GET https://example.com/api/v1/runners` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/api/v1/runners` If this points at an external API, prefix it …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com/api/v1/sessions (server/integration/sessions.test.ts:1286)
`server/integration/sessions.test.ts:1286` calls `GET https://example.com/api/v1/sessions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/api/v1/sessions` If this points at an external API, prefix…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://runner-session-channel/status (server/adapters/gateways/runner-channel.ts:13)
`server/adapters/gateways/runner-channel.ts:13` calls `GET https://runner-session-channel/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/runner-session-channel/status` If this points at an external AP…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/v1/auth/sessions (src/lib/oidc.ts:119)
`src/lib/oidc.ts:119` calls `POST /api/v1/auth/sessions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/v1/auth/sessions` 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://example.com/api/v1/agents (server/integration/agents.test.ts:54)
`server/integration/agents.test.ts:54` calls `POST https://example.com/api/v1/agents` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/api/v1/agents` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://example.com/api/v1/agents (server/integration/agents.test.ts:70)
`server/integration/agents.test.ts:70` calls `POST https://example.com/api/v1/agents` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/api/v1/agents` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://example.com/api/v1/auth/sessions (server/integration/auth.test.ts:84)
`server/integration/auth.test.ts:84` calls `POST https://example.com/api/v1/auth/sessions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/api/v1/auth/sessions` If this points at an external API, p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://example.com/api/v1/environments (server/integration/environments.test.ts:74)
`server/integration/environments.test.ts:74` calls `POST https://example.com/api/v1/environments` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/api/v1/environments` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://example.com/api/v1/environments (server/integration/environments.test.ts:90)
`server/integration/environments.test.ts:90` calls `POST https://example.com/api/v1/environments` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/api/v1/environments` If this points at an external …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://example.com/api/v1/runtime/workers-ai/v1/chat/completions (server/integration/runtime-ai.test.ts:6)
`server/integration/runtime-ai.test.ts:6` calls `POST https://example.com/api/v1/runtime/workers-ai/v1/chat/completions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/api/v1/runtime/workers-ai/v1…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://example.com/api/v1/vaults (server/integration/vaults.test.ts:27)
`server/integration/vaults.test.ts:27` calls `POST https://example.com/api/v1/vaults` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/api/v1/vaults` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://runner-session-channel/dispatch (server/adapters/gateways/runner-channel.ts:24)
`server/adapters/gateways/runner-channel.ts:24` calls `POST https://runner-session-channel/dispatch` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/runner-session-channel/dispatch` If this points at an extern…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT https://example.com/api/v1/runners/runner_x/heartbeat (server/integration/runners.test.ts:280)
`server/integration/runners.test.ts:280` calls `PUT https://example.com/api/v1/runners/runner_x/heartbeat` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com/api/v1/runners/runner_x/heartbeat` If this…
Dangling fetchFetch
high System graph security security conf 1.00 Insecure pattern 'exec_used' in runtime-bridge/src/providers/ama.ts:268
Found a known-risky pattern (exec_used). Review and replace if possible.
runtime-bridge/src/providers/ama.ts:268 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in server/adapters/runtime/sandbox-runtime-host.ts:140
Found a known-risky pattern (exec_used). Review and replace if possible.
server/adapters/runtime/sandbox-runtime-host.ts:140 Exec used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — e2e/fixtures.ts:27
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 — scripts/generate-openapi-and-sdks.ts:82
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 — sdk/typescript/src/index.ts:53
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 — server/adapters/gateways/runner-channel.ts:13
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 — server/adapters/gateways/secret-store.ts:49
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 — server/api-contracts.test.ts:15
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 — server/auth/oidc.ts:132
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 — server/http/leases.ts:288
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 — server/integration/access-rules.test.ts:6
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 — server/integration/agents.test.ts:6
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 — server/integration/audit-records.test.ts:6
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 — server/integration/auth.test.ts:10
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 — server/integration/budgets.test.ts:6
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 — server/integration/connections.test.ts:6
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 — server/integration/connectors.test.ts:6
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 — server/integration/effective-policy.test.ts:8
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 — server/integration/environments.test.ts:6
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 — server/integration/federated-tenants.test.ts:6
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 — server/integration/health.test.ts:7
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 — server/integration/leases.test.ts:10
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 — server/integration/openapi.test.ts:46
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 — server/integration/policies.test.ts:6
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 — server/integration/providers-governance.test.ts:6
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 — server/integration/providers.test.ts:10
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 — server/integration/restish-openapi.test.ts:17
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 — server/integration/runners.test.ts:9
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 — server/integration/runtime-ai.test.ts:6
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 — server/integration/runtimes.test.ts:6
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 — server/integration/sdk-contract.test.ts:8
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 — server/integration/sessions.test.ts:11
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 — server/integration/triggers.test.ts:6
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 — server/integration/usage-records.test.ts:10
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 — server/integration/usage-summary.test.ts:10
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 — server/integration/vaults.test.ts:7
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 — server/integration/work-items.test.ts:9
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 — server/worker.ts:14
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 — server/worker/runner-session-channel.ts:30
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 lockfile. 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: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph quality Integrity conf 1.00 Frontend route `/agents/:agentId` has no Link/navigate to it — src/features/agents/AgentDetailPage.test.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
Orphan pageWiring
medium System graph quality Integrity conf 1.00 Frontend route `/audit/:recordId` has no Link/navigate to it — src/features/audit/audit-ui.test.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
Orphan pageWiring
medium System graph quality Integrity conf 1.00 Frontend route `/environments/:environmentId` has no Link/navigate to it — src/features/environments/environments-ui.test.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
Orphan pageWiring
medium System graph quality Integrity conf 1.00 Frontend route `/mcp/:connectorId` has no Link/navigate to it — src/features/mcp/mcp-ui.test.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
Orphan pageWiring
medium System graph quality Integrity conf 1.00 2 occurrences Frontend route `/providers/:providerId` has no Link/navigate to it — src/features/providers/providers-ui.test.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
2 occurrences
repo-level (2 hits)
Orphan pageWiring
medium System graph quality Integrity conf 1.00 Frontend route `/sessions/:sessionId` has no Link/navigate to it — src/features/sessions/sessions-pages.test.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
Orphan pageWiring
medium System graph quality Integrity conf 1.00 Frontend route `/vaults/:vaultId` has no Link/navigate to it — src/features/vaults/vaults-ui.test.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
Orphan pageWiring
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/ama-runner-release.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in e2e/fixtures.ts:56
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
e2e/fixtures.ts:56 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in runtime-bridge/src/providers/ama.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
runtime-bridge/src/providers/ama.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in runtime-bridge/src/providers/claude-code.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
runtime-bridge/src/providers/claude-code.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in runtime-bridge/src/providers/cli-host.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
runtime-bridge/src/providers/cli-host.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in runtime-bridge/src/providers/copilot.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
runtime-bridge/src/providers/copilot.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/generate-go-contract.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/generate-go-contract.ts:1 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/smoke-runtime.mjs:11
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/smoke-runtime.mjs:11 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 47 placeholder/mock markers across 15 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 10 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `AMA_ACCESS_TOKEN`, `AMA_RUNTIME_BRIDGE_TEST_MODE`, `CI`, `CLOUDFLARE_ENV`, `E2E_APP_PORT`, `E2E_BASE_URL`, `E2E_PORT`, `HOME` + 2 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 14 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: docker.io/cloudflare/sandbox:0.10.1
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:1 containersPinned dependencies
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: sdk/typescript/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
sdk/typescript/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `org_old` in server/domain/policy.test.ts:118
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 `session_old` in src/features/sessions/sessions-pages.test.tsx:1794
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 Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/check-spec-coverage.ts:69
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/check-type-escapes.ts:80
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/generate-go-contract.ts:73
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: ALL /api/v1/runtime/sessions/:sessionId/*
`server/http/runtime-proxy.ts` declares `ALL /api/v1/runtime/sessions/:sessionId/*` 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 consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/docs
`server/app.ts` declares `GET /api/v1/docs` 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 /assistants
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /assistants` 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 /audio/speech
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /audio/speech` 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 /audio/transcriptions
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /audio/transcriptions` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /audio/translations
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /audio/translations` 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 /batches
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /batches` 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 /chat/completions
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /chat/completions` 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 /chatkit/sessions
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /chatkit/sessions` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /completions
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /completions` 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 /containers
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /containers` 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 /conversations
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /conversations` 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 /embeddings
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /embeddings` 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 /evals
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /evals` 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 /files
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /files` 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 /fine_tuning/alpha/graders/run
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /fine_tuning/alpha/graders/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 c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /fine_tuning/alpha/graders/validate
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /fine_tuning/alpha/graders/validate` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /fine_tuning/jobs
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /fine_tuning/jobs` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /images/edits
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /images/edits` 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 /images/generations
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /images/generations` 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 /images/variations
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /images/variations` 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 /moderations
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /moderations` 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 /realtime/client_secrets
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /realtime/client_secrets` 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 consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /realtime/sessions
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /realtime/sessions` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /realtime/transcription_sessions
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /realtime/transcription_sessions` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /responses
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /responses` 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 /responses/compact
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /responses/compact` 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 /responses/input_tokens
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /responses/input_tokens` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /skills
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /skills` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /threads
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /threads` 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 /threads/runs
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /threads/runs` 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 /uploads
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /uploads` 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 /v1/agents?beta=true
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /v1/agents?beta=true` 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 /v1/complete
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /v1/complete` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /v1/environments?beta=true
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /v1/environments?beta=true` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /v1/files?beta=true
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /v1/files?beta=true` 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 /v1/memory_stores?beta=true
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /v1/memory_stores?beta=true` 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 cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /v1/messages
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /v1/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 /v1/messages/batches
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /v1/messages/batches` 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 /v1/messages/batches?beta=true
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /v1/messages/batches?beta=true` 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 c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /v1/messages/count_tokens
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /v1/messages/count_tokens` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /v1/messages/count_tokens?beta=true
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /v1/messages/count_tokens?beta=true` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /v1/messages?beta=true
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /v1/messages?beta=true` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /v1/sessions?beta=true
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /v1/sessions?beta=true` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /v1/skills?beta=true
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /v1/skills?beta=true` 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 /v1/user_profiles?beta=true
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /v1/user_profiles?beta=true` 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 cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /v1/vaults?beta=true
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /v1/vaults?beta=true` 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 /vector_stores
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /vector_stores` 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 /videos
`cmd/ama-runner/runtime_bridge_bundle.mjs` declares `POST /videos` 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: USE /*
`server/app.ts` declares `USE /*` 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: cmd/ama-runner/runner_test.go (1486 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: server/integration/sessions.test.ts (1759 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: server/usecases/ports.ts (2600 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/features/sessions/sessions-pages.test.tsx (2161 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/features/vaults/vaults-ui.test.tsx (1424 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/44ab7bfe-61e9-49da-9da6-678a52035eb9/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/44ab7bfe-61e9-49da-9da6-678a52035eb9/

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.