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

Shyden-Ltd/ShyTalk

https://github.com/Shyden-Ltd/ShyTalk · scanned 2026-06-16 00:12 UTC (2 months, 2 weeks ago)

493 raw signals (0 security + 493 graph)

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

Complete repo analysis

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

JSON
Combined
46.7
/100
Security checks
47
0 findings
System graph
47
88.9% cov · 449 findings
Critical
2
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 2 High 18 Medium 55 Low 120 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 449 Crowd 0 Layer: Frontend 26 Network 3 Hardware 1 Security 35 Cicd 2 Quality 314 Api 68
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 46.7/100 with 88.9% coverage. It contains 5038 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 493 findings — concentrated in quality (314), security (70), api (68). Risk profile is high: 37 critical, 18 high, 64 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 194 of 449 actionable findings. 493 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 System graph security Secrets conf 1.00 Possible secret in .github/workflows/manual-qa-matrix.yml
Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.
.github/workflows/manual-qa-matrix.yml:128
critical System graph security Secrets conf 1.00 36 occurrences Possible secret in public/portal/portal-translations.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 79, 81, 191, 193, 299, 301, 403, 405, +28 more
public/portal/portal-translations.js:79, 81, 191, 193, 299, 301, 403, 405, +28 more (36 hits)
high System graph api Wiring conf 1.00 Dangling fetch: GET /events/events.json (public/js/seasonal-theme.js:32)
`public/js/seasonal-theme.js:32` calls `GET /events/events.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/events/events.json` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /favicon.ico (tests/web/logger-idempotency.spec.ts:71)
`tests/web/logger-idempotency.spec.ts:71` calls `GET /favicon.ico` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/favicon.ico` 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: GET /js/core/ui.js (tests/web/admin-core-modules.spec.ts:37)
`tests/web/admin-core-modules.spec.ts:37` calls `GET /js/core/ui.js` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/js/core/ui.js` 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: GET /js/roadmap-auth.js (tests/web/roadmap-auth.spec.ts:1288)
`tests/web/roadmap-auth.spec.ts:1288` calls `GET /js/roadmap-auth.js` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/js/roadmap-auth.js` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /js/roadmap-auth.js (tests/web/roadmap-auth.spec.ts:1298)
`tests/web/roadmap-auth.spec.ts:1298` calls `GET /js/roadmap-auth.js` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/js/roadmap-auth.js` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /js/roadmap-auth.js (tests/web/roadmap-auth.spec.ts:1307)
`tests/web/roadmap-auth.spec.ts:1307` calls `GET /js/roadmap-auth.js` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/js/roadmap-auth.js` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /js/roadmap-auth.js (tests/web/roadmap-auth.spec.ts:1317)
`tests/web/roadmap-auth.spec.ts:1317` calls `GET /js/roadmap-auth.js` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/js/roadmap-auth.js` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /js/roadmap-auth.js (tests/web/roadmap-auth.spec.ts:1337)
`tests/web/roadmap-auth.spec.ts:1337` calls `GET /js/roadmap-auth.js` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/js/roadmap-auth.js` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /js/suggestions-board.js (tests/web/suggestions-board.spec.ts:2322)
`tests/web/suggestions-board.spec.ts:2322` calls `GET /js/suggestions-board.js` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/js/suggestions-board.js` 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 /portal/portal.js (tests/web/portal-auth.spec.ts:507)
`tests/web/portal-auth.spec.ts:507` calls `GET /portal/portal.js` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/portal/portal.js` 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: GET /portal/portal.js (tests/web/portal-auth.spec.ts:519)
`tests/web/portal-auth.spec.ts:519` calls `GET /portal/portal.js` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/portal/portal.js` 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: GET /portal/portal.js (tests/web/portal-auth.spec.ts:541)
`tests/web/portal-auth.spec.ts:541` calls `GET /portal/portal.js` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/portal/portal.js` 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: GET /roadmap-data.json (public/admin/js/tabs/suggestions.js:849)
`public/admin/js/tabs/suggestions.js:849` calls `GET /roadmap-data.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/roadmap-data.json` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /roadmap-data.json (public/js/roadmap-app.js:1291)
`public/js/roadmap-app.js:1291` calls `GET /roadmap-data.json` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/roadmap-data.json` 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: GET http://ip-api.com/json/${ip}?fields=isp,as,country,regionName (express-api/src/routes/device-info.js:49)
`express-api/src/routes/device-info.js:49` calls `GET http://ip-api.com/json/${ip}?fields=isp,as,country,regionName` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/ip-api.com/json/<p>` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:8080 (local/seed.js:67)
`local/seed.js:67` calls `GET http://localhost:8080` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:8080` 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: GET https://api.appstoreconnect.apple.com${path} (scripts/ensure-testflight-auto-distribution.js:71)
`scripts/ensure-testflight-auto-distribution.js:71` calls `GET https://api.appstoreconnect.apple.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:/api.appstoreconnect.apple.com/<p>` If this points at…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.cloudflare.com/client/v4${path} (scripts/add-dns-records.mjs:23)
`scripts/add-dns-records.mjs:23` calls `GET https://api.cloudflare.com/client/v4${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.cloudflare.com/client/v4/<p>` If this points at an external API, pre…
Dangling fetchFetch
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — express-api/scripts/device-journey-runner.js:717
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 — express-api/scripts/manual-qa-runner.js:928
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 — express-api/src/routes/test-helpers.js:502
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 — express-api/src/utils/playStore.js:64
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 — public/admin/js/tabs/backups.js:5
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 — public/admin/js/tabs/economy-config.js:121
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 — public/admin/js/tabs/logs.js:956
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 — public/admin/js/tabs/maintenance.js:5
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 — public/js/core/api.js:33
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 — public/js/roadmap-app.js:1130
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 — public/portal/portal.js:164
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/add-dns-records.mjs:23
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/ensure-testflight-auto-distribution.js:71
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/lib/google-translate.js:28
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/settings.json
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/settings.json VerificationClaude instruction
medium System graph quality 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 10 occurrences 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.
10 files, 10 locations
.github/workflows/allure-report.yml
.github/workflows/dependabot-auto-merge.yml
.github/workflows/deploy-dev.yml
.github/workflows/e2e-tests.yml
.github/workflows/playwright-tests.yml
.github/workflows/pr-checks.yml
.github/workflows/release-tag.yml
.github/workflows/release.yml
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin/js/nuclear-reset.js:178
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin/js/nuclear-reset.js:178 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin/js/tabs/appeals.js:53
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin/js/tabs/appeals.js:53 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin/js/tabs/audit-log.js:59
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin/js/tabs/audit-log.js:59 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin/js/tabs/devices.js:115
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin/js/tabs/devices.js:115 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin/js/tabs/economy-config.js:231
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin/js/tabs/economy-config.js:231 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin/js/tabs/gifts.js:112
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin/js/tabs/gifts.js:112 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin/js/tabs/logs.js:862
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin/js/tabs/logs.js:862 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin/js/tabs/reports.js:397
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin/js/tabs/reports.js:397 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin/js/tabs/spin-monitor.js:339
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin/js/tabs/spin-monitor.js:339 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin/js/tabs/starting-screens.js:162
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin/js/tabs/starting-screens.js:162 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin/js/tabs/suggestions.js:260
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin/js/tabs/suggestions.js:260 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/admin/js/tabs/users.js:94
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/admin/js/tabs/users.js:94 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/event-translations.js:735
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/event-translations.js:735 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/language-selector.js:124
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/language-selector.js:124 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/legal-translations.js:139
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/legal-translations.js:139 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/preview-watermark.js:133
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/preview-watermark.js:133 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/roadmap-app.js:560
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/roadmap-app.js:560 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/roadmap-auth.js:49
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/roadmap-auth.js:49 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/seasonal-theme.js:105
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/seasonal-theme.js:105 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/js/suggestions-board.js:675
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/js/suggestions-board.js:675 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/portal/portal.js:449
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/portal/portal.js:449 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in public/js/shared-header.js:88
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
public/js/shared-header.js:88 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in public/js/suggestions-board.js:457
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
public/js/suggestions-board.js:457 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in public/js/logger.js:30
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
public/js/logger.js:30 Local storage auth token
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in express-api/scripts/device-journey-runner.js:59
Found a known-risky pattern (node_child_process). Review and replace if possible.
express-api/scripts/device-journey-runner.js:59 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in express-api/scripts/drivers/android-adb-driver.js:36
Found a known-risky pattern (node_child_process). Review and replace if possible.
express-api/scripts/drivers/android-adb-driver.js:36 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in express-api/scripts/drivers/android-cdp-helpers.js:24
Found a known-risky pattern (node_child_process). Review and replace if possible.
express-api/scripts/drivers/android-cdp-helpers.js:24 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in express-api/scripts/drivers/ios-appium-driver.js:48
Found a known-risky pattern (node_child_process). Review and replace if possible.
express-api/scripts/drivers/ios-appium-driver.js:48 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in express-api/scripts/drivers/ios-devicectl-driver.js:46
Found a known-risky pattern (node_child_process). Review and replace if possible.
express-api/scripts/drivers/ios-devicectl-driver.js:46 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in express-api/scripts/drivers/ios-simctl-driver.js:33
Found a known-risky pattern (node_child_process). Review and replace if possible.
express-api/scripts/drivers/ios-simctl-driver.js:33 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in express-api/scripts/drivers/web-mobile-firefox-android-driver.js:42
Found a known-risky pattern (node_child_process). Review and replace if possible.
express-api/scripts/drivers/web-mobile-firefox-android-driver.js:42 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in express-api/scripts/env-health-check.js:21
Found a known-risky pattern (node_child_process). Review and replace if possible.
express-api/scripts/env-health-check.js:21 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in express-api/src/cron/serverHealth.js:11
Found a known-risky pattern (node_child_process). Review and replace if possible.
express-api/src/cron/serverHealth.js:11 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 69 placeholder/mock markers across 31 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 network Security conf 1.00 Privileged port 12 in use
Port 12 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/branch-audit-snapshot.sh Ports
medium System graph network Security conf 1.00 Privileged port 34 in use
Port 34 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
scripts/branch-audit-snapshot.sh Ports
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 55 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ALLURE_ENABLED`, `ALLURE_PROJECT`, `ANDROID_SERIAL`, `APPIUM_BASE_URL`, `APPLE_APP_STORE_APP_ID`, `APP_STORE_CONNECT_ISSUER_ID`, `APP_STORE_CONNECT_KEY_ID`, `APP_STORE_CONNECT_KEY_PATH` + 47 more. Add them (with a placeholder/comment) to .env.exam…
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 183 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `claude_old` in express-api/tests/scripts/translate-strings.test.js: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 quality Integrity conf 1.00 Old/deprecated-named symbol `enroll_copy` in public/portal/portal-translations.js:40
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 `enroll_copy` in public/portal/portal.js:1170
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 `enroll_copy` in tests/web/portal-a11y.spec.ts:228
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 `enroll_copy` in tests/web/portal-aria-label-i18n.spec.ts:16
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 `enroll_copy` in tests/web/portal-totp-status-i18n.spec.ts:20
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 `footer_copy` in public/js/legal-translations.js:10
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 `footer_copy` in tests/web/homepage-footer-links-i18n.spec.ts:48
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 `footer_copy` in tests/web/legal-footer-i18n.spec.ts:91
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_old` in express-api/tests/routes/test-helpers-lifecycle.test.js:304
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 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 — assets/generate-mipmaps.js:121
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 — assets/generate.js:315
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 — express-api/scripts/dev-osa-data-probe.js: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 — express-api/scripts/device-journey-runner.js:306
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 — express-api/scripts/driver-surface-report.js:133
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 — express-api/scripts/env-health-check.js:12
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 — express-api/scripts/manual-qa-runner.js:15897
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 — express-api/scripts/migrate-participant-ids.js:65
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 — express-api/scripts/personas-csv-export.js:138
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 — express-api/scripts/provision-test-personas.js:572
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 — express-api/scripts/qa-allure-emit.js:165
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 — express-api/scripts/qa-html-report.js:143
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 — express-api/scripts/qa-result-diff.js:173
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 — express-api/scripts/seed-personas-local.js:46
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 — express-api/src/index.js:302
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 — express-api/tests/utils/consoleLogger.test.js:43
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 — local/seed.js:35
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/ensure-testflight-auto-distribution.js:89
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-allure-index.js:255
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-allure-landing.js:201
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-roadmap-json.js:184
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/translate-admin-strings.js:522
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/translate-strings.js:174
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/web/admin-console-errors.spec.ts:156
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/web/console-errors-all-pages.spec.ts:48
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/web/global-setup.ts:44
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 /gifts/:id
`express-api/src/routes/admin-gifts.js` declares `DELETE /gifts/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /rooms/:roomId/hosts/:userId
`express-api/src/routes/room-mutations.js` declares `DELETE /rooms/:roomId/hosts/:userId` 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: GET /api/health
`express-api/src/index.js` 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: PATCH /rooms/:roomId/name
`express-api/src/routes/room-mutations.js` declares `PATCH /rooms/:roomId/name` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PATCH /rooms/:roomId/require-approval
`express-api/src/routes/room-mutations.js` declares `PATCH /rooms/:roomId/require-approval` 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: PATCH /rooms/:roomId/seats/:seatIndex/mute
`express-api/src/routes/room-mutations.js` declares `PATCH /rooms/:roomId/seats/:seatIndex/mute` 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 /admin/maintenance/clear-subscriptions
`express-api/src/routes/suggestions-maintenance.js` declares `POST /admin/maintenance/clear-subscriptions` 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: POST /admin/maintenance/clear-suggestions
`express-api/src/routes/suggestions-maintenance.js` declares `POST /admin/maintenance/clear-suggestions` 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: POST /gifts
`express-api/src/routes/admin-gifts.js` declares `POST /gifts` 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 /rooms/:roomId/close
`express-api/src/routes/room-mutations.js` declares `POST /rooms/:roomId/close` 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 /rooms/:roomId/decline-invite
`express-api/src/routes/room-mutations.js` declares `POST /rooms/:roomId/decline-invite` 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: POST /rooms/:roomId/disconnect-user
`express-api/src/routes/room-mutations.js` declares `POST /rooms/:roomId/disconnect-user` 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 /rooms/:roomId/first-join
`express-api/src/routes/room-mutations.js` declares `POST /rooms/:roomId/first-join` 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 /rooms/:roomId/hosts
`express-api/src/routes/room-mutations.js` declares `POST /rooms/:roomId/hosts` 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 /rooms/:roomId/join
`express-api/src/routes/room-mutations.js` declares `POST /rooms/:roomId/join` 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 /rooms/:roomId/kick
`express-api/src/routes/room-mutations.js` declares `POST /rooms/:roomId/kick` 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 /rooms/:roomId/leave
`express-api/src/routes/room-mutations.js` declares `POST /rooms/:roomId/leave` 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 /rooms/:roomId/owner-away
`express-api/src/routes/room-mutations.js` declares `POST /rooms/:roomId/owner-away` 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 /rooms/:roomId/owner-returned
`express-api/src/routes/room-mutations.js` declares `POST /rooms/:roomId/owner-returned` 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: POST /rooms/:roomId/seats/:seatIndex/accept-invite
`express-api/src/routes/room-mutations.js` declares `POST /rooms/:roomId/seats/:seatIndex/accept-invite` 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: POST /rooms/:roomId/seats/:seatIndex/claim
`express-api/src/routes/room-mutations.js` declares `POST /rooms/:roomId/seats/:seatIndex/claim` 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 /rooms/:roomId/seats/:seatIndex/leave
`express-api/src/routes/room-mutations.js` declares `POST /rooms/:roomId/seats/:seatIndex/leave` 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 /rooms/:roomId/seats/:seatIndex/move
`express-api/src/routes/room-mutations.js` declares `POST /rooms/:roomId/seats/:seatIndex/move` 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 /rooms/:roomId/seats/:seatIndex/remove
`express-api/src/routes/room-mutations.js` declares `POST /rooms/:roomId/seats/:seatIndex/remove` 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: PUT /gifts/:id
`express-api/src/routes/admin-gifts.js` declares `PUT /gifts/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /admin/maintenance
`express-api/src/routes/suggestions-maintenance.js` declares `USE /admin/maintenance` 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: USE /api
`express-api/src/index.js` declares `USE /api` 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 /api/age-verification
`express-api/src/index.js` declares `USE /api/age-verification` 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 /api/appeals
`express-api/src/index.js` declares `USE /api/appeals` 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 /api/conversations
`express-api/src/index.js` declares `USE /api/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: USE /api/economy/backpack-send
`express-api/src/index.js` declares `USE /api/economy/backpack-send` 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 /api/economy/gacha
`express-api/src/index.js` declares `USE /api/economy/gacha` 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 /api/economy/gift
`express-api/src/index.js` declares `USE /api/economy/gift` 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 /api/economy/gift-batch
`express-api/src/index.js` declares `USE /api/economy/gift-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: USE /api/economy/gift-direct
`express-api/src/index.js` declares `USE /api/economy/gift-direct` 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 /api/economy/purchase
`express-api/src/index.js` declares `USE /api/economy/purchase` 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 /api/economy/trial-activate
`express-api/src/index.js` declares `USE /api/economy/trial-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 who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/economy/trial-claim
`express-api/src/index.js` declares `USE /api/economy/trial-claim` 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 /api/notifications
`express-api/src/index.js` declares `USE /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 consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/portal
`express-api/src/index.js` declares `USE /api/portal` 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 /api/portal/totp-recovery
`express-api/src/index.js` declares `USE /api/portal/totp-recovery` 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 /api/reports
`express-api/src/index.js` declares `USE /api/reports` 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 /api/translate
`express-api/src/index.js` declares `USE /api/translate` 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 /api/user/:uniqueId/cohort-override
`express-api/src/index.js` declares `USE /api/user/:uniqueId/cohort-override` 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 /api/users/:uniqueId/data-export
`express-api/src/index.js` declares `USE /api/users/:uniqueId/data-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 consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /api/users/:uniqueId/delete
`express-api/src/index.js` declares `USE /api/users/:uniqueId/delete` 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 /api/users/:uniqueId/pm-lock-check
`express-api/src/index.js` declares `USE /api/users/:uniqueId/pm-lock-check` 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 /api/users/discover
`express-api/src/index.js` declares `USE /api/users/discover` 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 /api/users/search
`express-api/src/index.js` declares `USE /api/users/search` 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 /gifts
`express-api/src/routes/admin-gifts.js` declares `USE /gifts` 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: express-api/scripts/device-journey-runner.js (1513 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: express-api/scripts/drivers/android-adb-driver.js (2848 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: express-api/scripts/manual-qa-runner.js (16467 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: express-api/src/routes/admin-users.js (1801 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: express-api/src/routes/economy.js (2026 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: express-api/src/routes/reports.js (1561 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: express-api/src/routes/suggestions.js (1954 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: express-api/src/routes/users.js (1498 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: express-api/tests/routes/admin-users-write.test.js (1488 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: express-api/tests/routes/reports-coverage-reports-core-a.test.js (2000 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: express-api/tests/routes/room-mutations.test.js (1821 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: express-api/tests/routes/suggestions-contracts-b.test.js (1444 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: express-api/tests/scripts/drivers/android-adb-driver.test.js (17315 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: express-api/tests/scripts/drivers/ios-devicectl-driver.test.js (4981 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: express-api/tests/scripts/manual-qa-runner.test.js (26582 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: express-api/tests/scripts/migrate-segregation-relationships.test.js (2409 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: express-api/tests/scripts/sync-stories-to-issues-board-fields.test.js (2307 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: express-api/tests/utils/data-export-builder.test.js (1522 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: public/admin/js/tabs/users.js (1965 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: public/admin/translations.js (3452 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: public/js/roadmap-app.js (1334 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: public/js/suggestions-board.js (1547 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: public/portal/portal-translations.js (2283 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: scripts/sync-stories-to-issues.sh (1676 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/integration/10-firestore-cohort-rules.spec.ts (2149 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/web/admin-suggestions.spec.ts (1784 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/web/dev-smoke.spec.ts (1300 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/web/roadmap-auth.spec.ts (1353 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: tests/web/suggestions-board.spec.ts (2332 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/652362e1-0ebf-443b-9f28-04e8f20418fc/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/652362e1-0ebf-443b-9f28-04e8f20418fc/

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.