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.
64 of your 548 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 4.16s · analysis 86.46s · 17.3 MB · GitHub API rate-limit (preflight)

socketio/socket.io

https://github.com/socketio/socket.io · scanned 2026-06-05 09:06 UTC (5 days, 19 hours ago) · 10 languages

832 raw signals (382 security + 450 graph) 48th percentile · Javascript · medium (20-100K LoC) System graph score 48 (higher by 17)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 19 hours ago · v2 · 400 actionable findings from 2 signal sources. 207 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 25.1 0.25 6.28
testing_score 92.0 0.20 18.40
documentation_score 86.6 0.15 12.99
practices_score 74.0 0.15 11.10
code_quality 71.0 0.10 7.10
Overall 1.00 64.9
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 9 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/`.
9 matching findings on this repo
  • info Commented-code block (10 lines) in docs/engine.io-protocol/v3-test-suite/test-s…
  • info Commented-code block (5 lines) in packages/socket.io/lib/parent-namespace.ts:102
  • info Commented-code block (5 lines) in examples/cluster-nginx/server/public/main.js:…
  • info Commented-code block (5 lines) in examples/cluster-haproxy/server/public/main.j…
  • info Commented-code block (5 lines) in examples/cluster-traefik/server/public/main.j…
  • info Commented-code block (5 lines) in examples/chat/public/main.js:112
  • info Commented-code block (6 lines) in examples/nuxt-example/server/plugins/socket.i…
  • info Commented-code block (5 lines) in examples/cluster-httpd/server/public/main.js:…
  • info Commented-code block (5 lines) in examples/create-react-app-example/src/service…
View all commented-out code findings →
Config drift 4 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.
4 matching findings on this repo
  • low File has no detected symbols: packages/socket.io-client/babel.config.js
  • low File has no detected symbols: packages/socket.io-client/support/rollup.config.u…
  • low File has no detected symbols: packages/socket.io-client/support/rollup.config.e…
  • low File has no detected symbols: packages/socket.io-client/support/rollup.config.u…
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/4d28810e-b8c1-47a9-b235-f60f50ca4517/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/4d28810e-b8c1-47a9-b235-f60f50ca4517/

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.