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

Sk3tch-Dev-Ux/DayzServerController

https://github.com/Sk3tch-Dev-Ux/DayzServerController · scanned 2026-06-16 00:14 UTC (2 months, 2 weeks ago)

224 raw signals (30 security + 194 graph)

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

Complete repo analysis

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

JSON
Combined
60.2
/100
Security checks
60
10 findings
System graph
60
88.9% cov · 166 findings
Critical
4
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 4 High 12 Medium 34 Low 71 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 10 System graph 166 Crowd 0 Layer: Quality 80 Security 28 Frontend 8 Cicd 5 Api 55
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 60.2/100 with 88.9% coverage. It contains 3165 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 194 findings — concentrated in quality (98), api (55), security (27). Risk profile is high: 2 critical, 8 high, 57 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 121 of 176 actionable findings. 252 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.

critical Security checks quality Practices conf 0.82 Foundry mined mock as real or placeholder: Sk3tch-Dev-Ux/DayzServerController
Graph query export: Mock, sample, placeholder, or self-attested behavior treated as real Query id: mock_as_real_or_placeholder Query type: motif_query Intent: Hard negatives for fake completeness and missing real data paths. Motif: mock_as_real_or_placeholder Training usage: hard_negative Graph gol…
critical Security checks security auth conf 0.78 8 occurrences Foundry mined security auth guardrail gaps: Sk3tch-Dev-Ux/DayzServerController
Graph query export: Security/auth changes without enough guardrails Query id: security_auth_guardrail_gaps Query type: motif_query Intent: Assumption-check security/auth examples requiring stronger tests or CI. Motif: security_auth_without_guardrails Training usage: assumption_check Graph gold labe…
8 occurrences
repo-level (8 hits)
critical System graph security Secrets conf 1.00 Possible secret in backend/lib/server-actions/providers/inhouse.js
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
backend/lib/server-actions/providers/inhouse.js:32
critical System graph security Secrets conf 1.00 Possible secret in backend/routes/setup.routes.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
backend/routes/setup.routes.js:417
high Security checks quality Practices conf 0.84 5 occurrences Foundry mined bad chains: Sk3tch-Dev-Ux/DayzServerController
Comment chain pattern product: bad_chains Repo: Sk3tch-Dev-Ux/DayzServerController Thread: Sk3tch-Dev-Ux/DayzServerController#8 Outcome: not_resolved_or_not_observed Thread label: thread_has_human_issue_without_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source_graph_h…
5 occurrences
repo-level (5 hits)
high Security checks quality Practices conf 0.80 Foundry mined docs only runtime fix: Sk3tch-Dev-Ux/DayzServerController
Graph query export: Docs-only response to runtime or integration issue Query id: docs_only_runtime_fix Query type: motif_query Intent: Assumption-check examples where docs or claims are not enough proof. Motif: docs_only_runtime_fix Training usage: assumption_check Graph gold label: supported_by_ve…
high Security checks quality Quality conf 0.76 Foundry mined schema ui api mismatch: Sk3tch-Dev-Ux/DayzServerController
Graph query export: Schema, UI, and API mismatch Query id: schema_ui_api_mismatch Query type: motif_query Intent: Assumption-check examples for data-path consistency across layers. Motif: schema_ui_api_mismatch Training usage: assumption_check Graph gold label: needs_more_evidence Repo: Sk3tch-Dev-…
high Security checks quality Testing conf 0.78 9 occurrences Foundry mined test ci gap after feedback: Sk3tch-Dev-Ux/DayzServerController
Graph query export: Feedback exposes missing tests or CI Query id: test_ci_gap_after_feedback Query type: motif_query Intent: Hard negatives for feedback/fix chains without adequate guardrails. Motif: test_ci_gap_after_feedback Training usage: hard_negative Graph gold label: assumption_check Repo: …
9 occurrences
repo-level (9 hits)
high System graph api Wiring conf 1.00 Dangling fetch: GET https://steamcdn-a.akamaihd.net/client/installer/steamcmd.zip (backend/lib/steamcmd.js:86)
`backend/lib/steamcmd.js:86` calls `GET https://steamcdn-a.akamaihd.net/client/installer/steamcmd.zip` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/steamcdn-a.akamaihd.net/client/installer/steamcmd.zip` If …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.steampowered.com/ISteamRemoteStorage/GetPublishedFileDetails/v1/ (backend/lib/polling.js:131)
`backend/lib/polling.js:131` calls `POST https://api.steampowered.com/ISteamRemoteStorage/GetPublishedFileDetails/v1/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.steampowered.com/isteamremotestorage/g…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.steampowered.com/ISteamRemoteStorage/GetPublishedFileDetails/v1/ (backend/lib/polling.js:98)
`backend/lib/polling.js:98` calls `POST https://api.steampowered.com/ISteamRemoteStorage/GetPublishedFileDetails/v1/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.steampowered.com/isteamremotestorage/ge…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.steampowered.com/ISteamRemoteStorage/GetPublishedFileDetails/v1/ (backend/routes/mods.routes.js:35)
`backend/routes/mods.routes.js:35` calls `POST https://api.steampowered.com/ISteamRemoteStorage/GetPublishedFileDetails/v1/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.steampowered.com/isteamremotesto…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.steampowered.com/ISteamRemoteStorage/GetPublishedFileDetails/v1/ (backend/routes/workshop.routes.js:44)
`backend/routes/workshop.routes.js:44` calls `POST https://api.steampowered.com/ISteamRemoteStorage/GetPublishedFileDetails/v1/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.steampowered.com/isteamremot…
Dangling fetchFetch
high System graph security security conf 1.00 Insecure pattern 'exec_used' in backend/routes/health.routes.js:514
Found a known-risky pattern (exec_used). Review and replace if possible.
backend/routes/health.routes.js:514 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in backend/routes/system.routes.js:205
Found a known-risky pattern (exec_used). Review and replace if possible.
backend/routes/system.routes.js:205 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in README.md:291
Found a known-risky pattern (exec_used). Review and replace if possible.
README.md:291 Exec used
medium Security checks quality Practices conf 0.62 7 occurrences Foundry mined assumption checks: Sk3tch-Dev-Ux/DayzServerController
Comment chain pattern product: assumption_checks Repo: Sk3tch-Dev-Ux/DayzServerController Thread: Sk3tch-Dev-Ux/DayzServerController#6 Outcome: ambiguous_needs_more_evidence Thread label: thread_has_human_issue_without_fix_context Source graph label: source_backed_multi_signal_graph Reasons: source…
7 occurrences
repo-level (7 hits)
medium Security checks quality maintenance conf 0.70 14 occurrences Foundry mined blueprint gap alignment: Sk3tch-Dev-Ux/DayzServerController
Graph query export: Human feedback aligned with blueprint or architecture gaps Query id: blueprint_gap_alignment Query type: motif_query Intent: Curriculum-gap examples connecting issue threads to helicopter-view gaps. Motif: blueprint_gap_alignment Training usage: curriculum_gap Graph gold label: …
14 occurrences
repo-level (14 hits)
medium Security checks quality Practices conf 0.72 5 occurrences Foundry mined review feedback without structured fix: Sk3tch-Dev-Ux/DayzServerController
Graph query export: Review feedback without structured fix chain Query id: review_feedback_without_structured_fix Query type: motif_query Intent: Weak-supervision examples for review comments lacking a traceable fix. Motif: review_feedback_without_structured_fix Training usage: weak_supervision Gra…
5 occurrences
repo-level (5 hits)
medium Security checks quality Practices conf 0.70 7 occurrences Foundry mined unresolved feedback: Sk3tch-Dev-Ux/DayzServerController
Graph query export: Human feedback without linked fix evidence Query id: unresolved_feedback Query type: motif_query Intent: Negative/unresolved examples that should not be hallucinated into fixes. Motif: unlinked_feedback_needs_evidence Training usage: negative_or_unresolved Graph gold label: need…
7 occurrences
repo-level (7 hits)
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — backend/lib/steamcmd.js:86
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 — backend/routes/backup.routes.js:149
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 — web/frontend/src/pages/EconomyHubPage.jsx:74
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 quality Integrity conf 1.00 28 occurrences Frontend route `dashboard` has no Link/navigate to it — web/frontend/src/router.jsx
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.
28 occurrences
repo-level (28 hits)
Orphan pageWiring
medium System graph cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
softprops/action-gh-release@v2 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/release.yml:89 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/release.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in backend/lib/dzsa-publisher.js:115
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
backend/lib/dzsa-publisher.js:115 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in backend/lib/agent-updater.js:22
Found a known-risky pattern (node_child_process). Review and replace if possible.
backend/lib/agent-updater.js:22 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in backend/lib/backup-engine.js:10
Found a known-risky pattern (node_child_process). Review and replace if possible.
backend/lib/backup-engine.js:10 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in backend/lib/bot-manager.js:9
Found a known-risky pattern (node_child_process). Review and replace if possible.
backend/lib/bot-manager.js:9 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in backend/lib/firewall-manager.js:23
Found a known-risky pattern (node_child_process). Review and replace if possible.
backend/lib/firewall-manager.js:23 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in backend/lib/license/machine-id.js:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
backend/lib/license/machine-id.js:14 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in backend/lib/lifecycle-hooks.js:26
Found a known-risky pattern (node_child_process). Review and replace if possible.
backend/lib/lifecycle-hooks.js:26 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in backend/lib/polling.js:166
Found a known-risky pattern (node_child_process). Review and replace if possible.
backend/lib/polling.js:166 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in backend/lib/port-checker.js:10
Found a known-risky pattern (node_child_process). Review and replace if possible.
backend/lib/port-checker.js:10 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in backend/lib/process-manager.js:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
backend/lib/process-manager.js:7 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in backend/lib/service-installer.js:22
Found a known-risky pattern (node_child_process). Review and replace if possible.
backend/lib/service-installer.js:22 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in backend/lib/sidecar-manager.js:13
Found a known-risky pattern (node_child_process). Review and replace if possible.
backend/lib/sidecar-manager.js:13 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in backend/lib/steamcmd.js:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
backend/lib/steamcmd.js:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in backend/routes/deploy.routes.js:23
Found a known-risky pattern (node_child_process). Review and replace if possible.
backend/routes/deploy.routes.js:23 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in backend/routes/health.routes.js:17
Found a known-risky pattern (node_child_process). Review and replace if possible.
backend/routes/health.routes.js:17 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in backend/routes/system.routes.js:7
Found a known-risky pattern (node_child_process). Review and replace if possible.
backend/routes/system.routes.js:7 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in desktop/src/auto-updater.js:38
Found a known-risky pattern (node_child_process). Review and replace if possible.
desktop/src/auto-updater.js:38 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in desktop/src/install-paths.js:26
Found a known-risky pattern (node_child_process). Review and replace if possible.
desktop/src/install-paths.js:26 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in installer/build.js:21
Found a known-risky pattern (node_child_process). Review and replace if possible.
installer/build.js:21 Node child process
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in backend/lib/totp.js:84
Found a known-risky pattern (weak_hash). Review and replace if possible.
backend/lib/totp.js:84 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in docs/improvement-analysis/backlog.json:851
Found a known-risky pattern (weak_hash). Review and replace if possible.
docs/improvement-analysis/backlog.json:851 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in docs/improvement-analysis/README.md:78
Found a known-risky pattern (weak_hash). Review and replace if possible.
docs/improvement-analysis/README.md:78 Weak hash
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 165 placeholder/mock markers across 42 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Integrity conf 1.00 44 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ALLOW_INSECURE_BIND`, `CFTOOLS_API_BASE`, `CFTOOLS_APPLICATION_ID`, `CFTOOLS_SECRET`, `CITADEL_AGENT_SPAWN_BOT`, `CITADEL_CLOUD_BANS_SYNC_INTERVAL_MS`, `CITADEL_DATA_DIR`, `CITADEL_DEV` + 36 more. Add them (with a placeholder/comment) to .env.exam…
config drift
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 109 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph cicd CI/CD security conf 1.00 2 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
lines 18, 21
.github/workflows/release.yml:18, 21 (2 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Tests conf 1.00 Low test-to-source ratio
44 tests / 285 src (ratio 0.15).
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 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.
desktop/package.json CI/CD securitySupply chainNpm
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 — backend/lib/service-installer.js:189
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 — backend/lib/setup.js:26
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 — backend/server.js:644
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 — desktop/scripts/build-icons.js:45
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 — desktop/src/auto-updater.js:117
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 — desktop/src/main.js:178
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 — installer/build.js:101
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 — marketing/discord/post.js:64
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/audit/actions
`web/frontend/src/pages/AuditLogPage.jsx` declares `GET /api/audit/actions` 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/audit/users
`web/frontend/src/pages/AuditLogPage.jsx` declares `GET /api/audit/users` 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/citadel-license/status
`web/frontend/src/components/CitadelLicenseBanner.jsx` declares `GET /api/citadel-license/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenti…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/citadel-license/telemetry-state
`web/frontend/src/pages/CitadelLicensePage.jsx` declares `GET /api/citadel-license/telemetry-state` 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/cloud-bans/status
`web/frontend/src/components/CitadelLicenseBanner.jsx` declares `GET /api/cloud-bans/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/expansion-docs/field-index
`web/frontend/src/components/ConfigSearchModal.jsx` declares `GET /api/expansion-docs/field-index` 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/expansion-docs/templates
`web/frontend/src/utils/expansionDocsCache.js` declares `GET /api/expansion-docs/templates` 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: GET /api/notifications
`web/frontend/src/components/NotificationCenter.jsx` declares `GET /api/notifications` 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: GET /api/notifications/facets
`web/frontend/src/pages/NotificationsPage.jsx` declares `GET /api/notifications/facets` 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 con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/priority-queue
`web/frontend/src/pages/PriorityQueuePage.jsx` declares `GET /api/priority-queue` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/priority-queue/export
`web/frontend/src/pages/PriorityQueuePage.jsx` declares `GET /api/priority-queue/export` 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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/roles
`web/frontend/src/pages/UsersPage.jsx` declares `GET /api/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 who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/servers
`web/frontend/src/contexts/ServersContext.jsx` declares `GET /api/servers` 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/setup/network/detect
`web/frontend/src/pages/SetupWizardPage.jsx` declares `GET /api/setup/network/detect` 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: GET /api/setup/status
`web/frontend/src/router.jsx` declares `GET /api/setup/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/steam/status
`web/frontend/src/pages/SettingsPage.jsx` declares `GET /api/steam/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/system/config
`web/frontend/src/pages/SettingsPage.jsx` declares `GET /api/system/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/system/info
`web/frontend/src/pages/SystemDashboardPage.jsx` declares `GET /api/system/info` 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: GET /api/system/metrics
`web/frontend/src/pages/SystemDashboardPage.jsx` declares `GET /api/system/metrics` 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/updates/status
`web/frontend/src/components/CitadelUpdateBanner.jsx` declares `GET /api/updates/status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/users
`web/frontend/src/pages/UsersPage.jsx` declares `GET /api/users` 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/workshop/search?q=
`web/frontend/src/pages/ModsPage/ModsPage.jsx` declares `GET /api/workshop/search?q=` 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: PATCH /api/notifications/read
`web/frontend/src/components/NotificationCenter.jsx` declares `PATCH /api/notifications/read` 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: PATCH /api/servers/
`web/frontend/src/pages/ServerSettingsPage.jsx` declares `PATCH /api/servers/` 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: PATCH /api/system/config
`web/frontend/src/pages/SettingsPage.jsx` declares `PATCH /api/system/config` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/auth/login
`web/frontend/src/pages/LoginScreen.jsx` declares `POST /api/auth/login` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/auth/logout
`web/frontend/src/contexts/AuthContext.jsx` declares `POST /api/auth/logout` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/cftools-import/preview
`web/frontend/src/components/CFToolsImportModal.jsx` declares `POST /api/cftools-import/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 documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/cftools-import/run
`web/frontend/src/components/CFToolsImportModal.jsx` declares `POST /api/cftools-import/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 wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/citadel-license/activate
`web/frontend/src/pages/CitadelLicensePage.jsx` declares `POST /api/citadel-license/activate` 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: POST /api/citadel-license/refresh
`web/frontend/src/components/CitadelLicenseBanner.jsx` declares `POST /api/citadel-license/refresh` 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: POST /api/citadel-license/telemetry-toggle
`web/frontend/src/pages/CitadelLicensePage.jsx` declares `POST /api/citadel-license/telemetry-toggle` 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/deploy
`web/frontend/src/pages/DeployPage.jsx` declares `POST /api/deploy` 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/priority-queue
`web/frontend/src/pages/PriorityQueuePage.jsx` declares `POST /api/priority-queue` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/priority-queue/cleanup
`web/frontend/src/pages/PriorityQueuePage.jsx` declares `POST /api/priority-queue/cleanup` 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 /api/priority-queue/import
`web/frontend/src/pages/PriorityQueuePage.jsx` declares `POST /api/priority-queue/import` 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 /api/roles
`web/frontend/src/pages/UsersPage.jsx` declares `POST /api/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 who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/servers
`web/frontend/src/pages/DeployPage.jsx` declares `POST /api/servers` 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/servers/batch
`web/frontend/src/pages/ServerHubPage.jsx` declares `POST /api/servers/batch` 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/servers/detect
`web/frontend/src/pages/DeployPage.jsx` declares `POST /api/servers/detect` 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/setup/admin
`web/frontend/src/pages/SetupWizardPage.jsx` declares `POST /api/setup/admin` 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/setup/complete
`web/frontend/src/pages/SetupWizardPage.jsx` declares `POST /api/setup/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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/setup/network
`web/frontend/src/pages/SetupWizardPage.jsx` declares `POST /api/setup/network` 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/setup/steam
`web/frontend/src/pages/SetupWizardPage.jsx` declares `POST /api/setup/steam` 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/setup/steam/save
`web/frontend/src/pages/SetupWizardPage.jsx` declares `POST /api/setup/steam/save` 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 /api/setup/steam/validate
`web/frontend/src/pages/SetupWizardPage.jsx` declares `POST /api/setup/steam/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 who cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/steam/credentials
`web/frontend/src/pages/SettingsPage.jsx` declares `POST /api/steam/credentials` 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 /api/steam/credentials/save
`web/frontend/src/pages/SettingsPage.jsx` declares `POST /api/steam/credentials/save` 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 /api/updates/dismiss
`web/frontend/src/components/CitadelUpdateBanner.jsx` declares `POST /api/updates/dismiss` 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 /api/users
`web/frontend/src/pages/UsersPage.jsx` declares `POST /api/users` 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: backend/routes/actions.routes.js (1074 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: web/frontend/src/pages/EventsEditorPage.jsx (1625 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: web/frontend/src/pages/ExpansionEditorPage.jsx (3707 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: web/frontend/src/pages/QuestCreatorPage.jsx (1309 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: web/frontend/src/pages/SetupWizardPage.jsx (1202 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: web/frontend/src/pages/TraderEditorPage.jsx (2364 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/22a512b4-659a-4229-812d-4fa13769846e/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/22a512b4-659a-4229-812d-4fa13769846e/

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.