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

Crit-Fumble/cfg-core-server

https://github.com/Crit-Fumble/cfg-core-server · scanned 2026-06-17 01:25 UTC (1 month, 2 weeks ago)

235 raw signals (0 security + 235 graph)

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

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -2.8 (diff) · 235 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
73.9
/100
Security checks
74
0 findings
System graph
74
100.0% cov · 235 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 6 Medium 26 Low 63 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 235 Crowd 0 Layer: Frontend 20 Hardware 1 Security 6 Cicd 4 Quality 148 Api 56
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 73.9/100 with 100.0% coverage. It contains 4868 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 235 findings — concentrated in quality (148), api (56), frontend (20). Risk profile is high: 0 critical, 6 high, 26 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 95 of 235 actionable findings. 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: GET http://${containerName}:${internalPort}/api/ping (src/routes/v1/admin/chat-setup.ts:72)
`src/routes/v1/admin/chat-setup.ts:72` calls `GET http://${containerName}:${internalPort}/api/ping` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/<p>:/<p>/api/ping` If this points at an external API, prefix i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://discord.com/api/v10/users/@me (src/routes/v1/discord/linked-roles.ts:178)
`src/routes/v1/discord/linked-roles.ts:178` calls `GET https://discord.com/api/v10/users/@me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/users/@me` If this points at an external API, p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://www.worldanvil.com/api/aragorn/user (src/routes/v1/account/worldanvil.ts:282)
`src/routes/v1/account/worldanvil.ts:282` calls `GET https://www.worldanvil.com/api/aragorn/user` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/www.worldanvil.com/api/aragorn/user` If this points at an exter…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/oauth2/token (src/routes/config.ts:65)
`src/routes/config.ts:65` calls `POST https://discord.com/api/oauth2/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/oauth2/token` If this points at an external API, prefix it with `http…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://discord.com/api/v10/oauth2/token (src/routes/v1/discord/linked-roles.ts:158)
`src/routes/v1/discord/linked-roles.ts:158` calls `POST https://discord.com/api/v10/oauth2/token` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/oauth2/token` If this points at an external…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT https://discord.com/api/v10/channels/${channelId}/permissions/${overwriteId} (src/clients/discord/guild-api.ts:467)
`src/clients/discord/guild-api.ts:467` calls `PUT https://discord.com/api/v10/channels/${channelId}/permissions/${overwriteId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/discord.com/api/v10/channels/<p>/…
Dangling fetchFetch
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/register-resesh-commands.ts:95
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 — src/clients/discord/client.ts:59
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 — src/clients/discord/guild-api.ts:467
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 — src/config/server.ts:103
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 — src/plugins/auth.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 — src/routes/config.ts:65
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 — src/routes/internal/webhooks.ts:135
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 — src/routes/v1/account/worldanvil.ts:282
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 — src/routes/v1/discord/linked-roles.ts:158
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 — src/routes/v1/player/campaign-page-data.ts:264
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 — src/services/admin-alert.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 — src/services/auth/steam-provider.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 — src/services/discord/discord-service.ts:96
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 — src/services/discord/voice/recording-indicators.ts:578
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 — src/services/user-volume-storage/gid-allocator.ts:166
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 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 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/release.yml CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/publish-db.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in prisma/migrate.mjs:40
Found a known-risky pattern (node_child_process). Review and replace if possible.
prisma/migrate.mjs:40 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/check-route-collisions.mjs:22
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/check-route-collisions.mjs:22 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/services/foundry/foundry-backups.ts:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/services/foundry/foundry-backups.ts:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/services/foundry/foundry-worlds.ts:18
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/services/foundry/foundry-worlds.ts:18 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/services/user-volume-storage.ts:31
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/services/user-volume-storage.ts:31 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/services/user-volume-storage/host-group.ts:28
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/services/user-volume-storage/host-group.ts:28 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 30 placeholder/mock markers across 23 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 16 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ADMIN_DISCORD_IDS`, `CFG_CONTAINER_PLATFORM`, `CFG_FOUNDRY_PLUGIN_MANIFEST_URL`, `DISCORD_CLIENT_ID`, `DISRECORD_DISCORD_CLIENT_SECRET`, `DISRECORD_DISCORD_TOKEN`, `DOCKER_DEFAULT_PLATFORM`, `FOUNDRY_ADMIN_KEY` + 8 more. Add them (with a placehold…
config drift
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 58 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: node:24-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:27 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/release.yml:34 CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `core_game_creatures_legacy` in prisma/migrate-to-canonical-entities.ts:72
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 cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts
preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.
package.json CI/CD securitySupply chainNpm
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — prisma/backfill-world-access-grants.ts:286
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 — prisma/bootstrap.ts:30
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 — prisma/migrate-to-canonical-entities.ts:68
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/register-resesh-commands.ts:91
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 — src/cli/foundry-init.ts:39
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 — tests/helpers/docker.ts:225
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 — tests/helpers/screenshot-compare.ts:223
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: DELETE /api/v1/instances/:instanceType/:instanceId/roles
`src/routes/v1/instances.ts` declares `DELETE /api/v1/instances/:instanceType/:instanceId/roles` 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 documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/v1/player/campaigns/:campaignId/homebrew/:homebrewId
`src/routes/v1/player/campaign-homebrew.ts` declares `DELETE /api/v1/player/campaigns/:campaignId/homebrew/:homebrewId` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/v1/player/campaigns/:campaignId/quests/:questId
`src/routes/v1/player/campaign-quests.ts` declares `DELETE /api/v1/player/campaigns/:campaignId/quests/:questId` 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 removi…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/v1/player/campaigns/:campaignId/rules/:ruleId
`src/routes/v1/player/campaign-quests.ts` declares `DELETE /api/v1/player/campaigns/:campaignId/rules/:ruleId` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/v1/player/campaigns/:campaignId/scenes/:sceneId/log/:entryId
`src/routes/v1/player/campaign-scene-log.ts` declares `DELETE /api/v1/player/campaigns/:campaignId/scenes/:sceneId/log/:entryId` 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 —…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/v1/player/campaigns/:campaignId/tables/:tableId
`src/routes/v1/player/campaign-quests.ts` declares `DELETE /api/v1/player/campaigns/:campaignId/tables/:tableId` 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 removi…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/v1/player/compendium-sources/:slug
`src/routes/v1/player/compendium-sources.ts` declares `DELETE /api/v1/player/compendium-sources/:slug` 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 docu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/v1/player/compendium-sources/:slug/collaboration-sessions/:id
`src/routes/v1/player/compendium-sources.ts` declares `DELETE /api/v1/player/compendium-sources/:slug/collaboration-sessions/: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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/config
`src/routes/config.ts` declares `GET /api/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 /api/health
`src/routes/health.ts` declares `GET /api/health` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/instances/:instanceType/:instanceId/roles
`src/routes/v1/instances.ts` declares `GET /api/v1/instances/:instanceType/:instanceId/roles` 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 w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/player/campaigns/:campaignId/homebrew
`src/routes/v1/player/campaign-homebrew.ts` declares `GET /api/v1/player/campaigns/:campaignId/homebrew` 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 do…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/player/campaigns/:campaignId/homebrew/:homebrewId
`src/routes/v1/player/campaign-homebrew.ts` declares `GET /api/v1/player/campaigns/:campaignId/homebrew/:homebrewId` 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 re…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/player/campaigns/:campaignId/quests
`src/routes/v1/player/campaign-quests.ts` declares `GET /api/v1/player/campaigns/:campaignId/quests` 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 docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/player/campaigns/:campaignId/quests/:questId
`src/routes/v1/player/campaign-quests.ts` declares `GET /api/v1/player/campaigns/:campaignId/quests/:questId` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/player/campaigns/:campaignId/rules
`src/routes/v1/player/campaign-quests.ts` declares `GET /api/v1/player/campaigns/:campaignId/rules` 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 documen…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/player/campaigns/:campaignId/scenes/:sceneId/log
`src/routes/v1/player/campaign-scene-log.ts` declares `GET /api/v1/player/campaigns/:campaignId/scenes/:sceneId/log` 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 re…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/player/campaigns/:campaignId/scenes/:sceneId/log/from-chat
`src/routes/v1/player/campaign-scene-log.ts` declares `GET /api/v1/player/campaigns/:campaignId/scenes/:sceneId/log/from-chat` 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 — c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/player/campaigns/:campaignId/tables
`src/routes/v1/player/campaign-quests.ts` declares `GET /api/v1/player/campaigns/:campaignId/tables` 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 docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/player/campaigns/:campaignId/tables/:tableId
`src/routes/v1/player/campaign-quests.ts` declares `GET /api/v1/player/campaigns/:campaignId/tables/:tableId` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/player/campaigns/:id/key-terms
`src/routes/v1/player/campaign-key-terms.ts` declares `GET /api/v1/player/campaigns/:id/key-terms` 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 document…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/player/campaigns/:id/key-terms/preview
`src/routes/v1/player/campaign-key-terms.ts` declares `GET /api/v1/player/campaigns/:id/key-terms/preview` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/player/campaigns/:id/parties/:partyId/key-terms
`src/routes/v1/player/campaign-key-terms.ts` declares `GET /api/v1/player/campaigns/:id/parties/:partyId/key-terms` 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 rem…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/player/compendium-sources
`src/routes/v1/player/compendium-sources.ts` declares `GET /api/v1/player/compendium-sources` 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 w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/player/compendium-sources/:slug
`src/routes/v1/player/compendium-sources.ts` declares `GET /api/v1/player/compendium-sources/:slug` 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 documen…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/player/compendium-sources/:slug/chat-settings
`src/routes/v1/player/compendium-sources.ts` declares `GET /api/v1/player/compendium-sources/:slug/chat-settings` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider remov…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/v1/player/compendium-sources/:slug/collaboration-sessions
`src/routes/v1/player/compendium-sources.ts` declares `GET /api/v1/player/compendium-sources/:slug/collaboration-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 — consi…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/v1/player/campaigns/:campaignId/quests/:questId
`src/routes/v1/player/campaign-quests.ts` declares `PATCH /api/v1/player/campaigns/:campaignId/quests/:questId` 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 removin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/v1/player/campaigns/:campaignId/rules/:ruleId
`src/routes/v1/player/campaign-quests.ts` declares `PATCH /api/v1/player/campaigns/:campaignId/rules/:ruleId` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/v1/player/campaigns/:campaignId/tables/:tableId
`src/routes/v1/player/campaign-quests.ts` declares `PATCH /api/v1/player/campaigns/:campaignId/tables/:tableId` 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 removin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/v1/player/campaigns/:id/key-terms
`src/routes/v1/player/campaign-key-terms.ts` declares `PATCH /api/v1/player/campaigns/:id/key-terms` 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 docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/v1/player/campaigns/:id/parties/:partyId/key-terms
`src/routes/v1/player/campaign-key-terms.ts` declares `PATCH /api/v1/player/campaigns/:id/parties/:partyId/key-terms` 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 r…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/v1/player/compendium-sources/:slug
`src/routes/v1/player/compendium-sources.ts` declares `PATCH /api/v1/player/compendium-sources/:slug` 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 docum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/v1/player/compendium-sources/:slug/chat-settings
`src/routes/v1/player/compendium-sources.ts` declares `PATCH /api/v1/player/compendium-sources/:slug/chat-settings` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider rem…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/v1/player/compendium-sources/:slug/collaboration-sessions/:id
`src/routes/v1/player/compendium-sources.ts` declares `PATCH /api/v1/player/compendium-sources/:slug/collaboration-sessions/: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 —…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/config/token
`src/routes/config.ts` declares `POST /api/config/token` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/dice
`src/routes/v1/dice.ts` declares `POST /api/v1/dice` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/instances/:instanceType/:instanceId/roles
`src/routes/v1/instances.ts` declares `POST /api/v1/instances/:instanceType/:instanceId/roles` 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 /api/v1/player/campaigns/:campaignId/homebrew
`src/routes/v1/player/campaign-homebrew.ts` declares `POST /api/v1/player/campaigns/:campaignId/homebrew` 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 d…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/player/campaigns/:campaignId/homebrew/:homebrewId/approve
`src/routes/v1/player/campaign-homebrew.ts` declares `POST /api/v1/player/campaigns/:campaignId/homebrew/:homebrewId/approve` 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 — co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/player/campaigns/:campaignId/quests
`src/routes/v1/player/campaign-quests.ts` declares `POST /api/v1/player/campaigns/:campaignId/quests` 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 docum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/player/campaigns/:campaignId/rules
`src/routes/v1/player/campaign-quests.ts` declares `POST /api/v1/player/campaigns/:campaignId/rules` 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 docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/player/campaigns/:campaignId/scenes/:sceneId/log
`src/routes/v1/player/campaign-scene-log.ts` declares `POST /api/v1/player/campaigns/:campaignId/scenes/:sceneId/log` 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 r…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/player/campaigns/:campaignId/scenes/:sceneId/log/from-chat
`src/routes/v1/player/campaign-scene-log.ts` declares `POST /api/v1/player/campaigns/:campaignId/scenes/:sceneId/log/from-chat` 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 — …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/player/campaigns/:campaignId/tables
`src/routes/v1/player/campaign-quests.ts` declares `POST /api/v1/player/campaigns/:campaignId/tables` 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 docum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/player/campaigns/:campaignId/tables/:tableId/roll
`src/routes/v1/player/campaign-quests.ts` declares `POST /api/v1/player/campaigns/:campaignId/tables/:tableId/roll` 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 rem…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/player/compendium-sources
`src/routes/v1/player/compendium-sources.ts` declares `POST /api/v1/player/compendium-sources` 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 /api/v1/player/compendium-sources/:slug/collaboration-sessions
`src/routes/v1/player/compendium-sources.ts` declares `POST /api/v1/player/compendium-sources/:slug/collaboration-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 — cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/player/compendium-sources/:slug/submit-for-review
`src/routes/v1/player/compendium-sources.ts` declares `POST /api/v1/player/compendium-sources/:slug/submit-for-review` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/v1/player/compendium-sources/:slug/withdraw-review
`src/routes/v1/player/compendium-sources.ts` declares `POST /api/v1/player/compendium-sources/:slug/withdraw-review` 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 re…
Unused endpoint
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/e11d1de1-2113-42ea-9ec1-93a113ae73f6/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/e11d1de1-2113-42ea-9ec1-93a113ae73f6/

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.