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.

xingfanxia/guandan-online

https://github.com/xingfanxia/guandan-online · scanned 2026-06-16 01:03 UTC (2 months, 1 week ago)

132 raw signals (0 security + 132 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Commented-out code 117 findings
What it is: Lines of source that were intentionally disabled but never deleted.
Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.
How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.
Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.
12 matching findings on this repo
  • info Commented-code block (5 lines) in playwright.config.ts:42
  • info Commented-code block (6 lines) in vitest.config.ts:40
  • info Commented-code block (6 lines) in tests/security/ipThrottle.test.ts:7
  • info Commented-code block (6 lines) in tests/security/rateLimit.test.ts:75
  • info Commented-code block (5 lines) in tests/ai/enumerateSequences.test.ts:64
  • info Commented-code block (5 lines) in tests/ai/strength.test.ts:3
  • info Commented-code block (5 lines) in tests/ai/medium-decomposer.test.ts:30
  • info Commented-code block (5 lines) in tests/ai/decomposer/decompose.test.ts:129
  • info Commented-code block (6 lines) in tests/api/createRoom.test.ts:551
  • info Commented-code block (6 lines) in tests/api/startGame.test.ts:496
  • info Commented-code block (6 lines) in tests/api/sseConnectSnapshot.test.ts:3
  • info Commented-code block (6 lines) in tests/api/sse.test.ts:324
View all commented-out code findings →
Config drift 2 findings
What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.
Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.
How AI causes it: AI writes new config from memory rather than reading the existing source.
Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.
2 matching findings on this repo
  • info Commented-code block (5 lines) in playwright.config.ts:42
  • info Commented-code block (6 lines) in vitest.config.ts:40
View all config drift findings →
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/111ff12b-f2a6-4249-95c1-13971d347b19/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/111ff12b-f2a6-4249-95c1-13971d347b19/

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.