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

sheng-neo/ra2-web

https://github.com/sheng-neo/ra2-web · scanned 2026-06-16 00:10 UTC (2 months, 2 weeks ago)

36 raw signals (0 security + 36 graph)

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

Complete repo analysis

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

JSON
Combined
56.9
/100
Security checks
57
0 findings
System graph
57
88.9% cov · 35 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 5 Medium 16 Low 13 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 35 Crowd 0 Layer: Frontend 2 Hardware 3 Security 12 Cicd 2 Quality 9 Api 7
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 56.9/100 with 88.9% coverage. It contains 357 nodes across 8 cross-layer flows, written primarily in mixed languages. Engine surfaced 36 findings — concentrated in security (12), quality (9), api (7). Risk profile is high: 0 critical, 5 high, 16 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 34 of 35 actionable findings. 36 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph api Wiring conf 1.00 Dangling fetch: GET /api/witness (packages/client/src/pages/boot-screen.ts:415)
`packages/client/src/pages/boot-screen.ts:415` calls `GET /api/witness` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/witness` 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 /game-data/${casedName} (packages/client/src/game-files.ts:83)
`packages/client/src/game-files.ts:83` calls `GET /game-data/${casedName}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/game-data/<p>` 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 /game-data/${name} (packages/client/src/real-art.ts:125)
`packages/client/src/real-art.ts:125` calls `GET /game-data/${name}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/game-data/<p>` 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://127.0.0.1:${server.port}/health (packages/server/src/server.test.ts:65)
`packages/server/src/server.test.ts:65` calls `GET http://127.0.0.1:${server.port}/health` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:/<p>/health` If this points at an external API, prefix it wit…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/witness (packages/client/src/pages/boot-screen.ts:419)
`packages/client/src/pages/boot-screen.ts:419` calls `POST /api/witness` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/witness` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/server/src/server.test.ts:65
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing lockfile. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph hardware Security conf 1.00 Dockerfile runs as root: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
pnpm/action-setup@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/ci.yml:15 CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in packages/server/src/server.ts:36
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
packages/server/src/server.ts:36 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/client/src/main.ts:11
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
packages/client/src/main.ts:11 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/client/src/match-view.ts:246
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
packages/client/src/match-view.ts:246 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/client/src/pages/asset-browser.ts:80
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
packages/client/src/pages/asset-browser.ts:80 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/client/src/pages/boot-screen.ts:172
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
packages/client/src/pages/boot-screen.ts:172 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/client/src/pages/mp.ts:78
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
packages/client/src/pages/mp.ts:78 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/client/src/pages/play.ts:41
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
packages/client/src/pages/play.ts:41 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in packages/client/src/match-view.ts:315
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
packages/client/src/match-view.ts:315 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in packages/client/src/pages/asset-browser.ts:264
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
packages/client/src/pages/asset-browser.ts:264 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in packages/client/src/pages/map-viewer.ts:37
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
packages/client/src/pages/map-viewer.ts:37 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in packages/client/src/pages/sim-sandbox.ts:53
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
packages/client/src/pages/sim-sandbox.ts:53 Insert adjacent html
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
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 12 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: node:22-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 2, 13
Dockerfile:2, 13 (2 hits)
containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
actions/setup-node@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/ci.yml:18 CI/CD securitySupply chainGithub actions
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/client/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/client/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/game/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/game/package.json LockfileReproducibilityGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: packages/server/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
packages/server/package.json LockfileReproducibilityGenerated repo pattern
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 — packages/server/src/index.ts:14
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 — tools/check-assets.ts: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 api Wiring conf 1.00 Unused endpoint: USE /api/witness
`packages/client/vite.config.ts` declares `USE /api/witness` 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 /game-data
`packages/client/vite.config.ts` declares `USE /game-data` 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: packages/client/src/match-view.ts (1786 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/a8d8113f-8fb7-4cd6-b8d3-8cc1c14f132a/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/a8d8113f-8fb7-4cd6-b8d3-8cc1c14f132a/

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.