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.
20 of your 91 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • Clone from GitHub took 61.51s for a 67.9 MB repo slow.
  • Repobility's analysis ran in 8.89s after the clone landed.

GoMudEngine/GoMud

https://github.com/GoMudEngine/GoMud · scanned 2026-06-05 19:31 UTC (4 days, 16 hours ago) · 10 languages

272 raw signals (80 security + 192 graph) 11/13 scanners ran 48th percentile · Go · large (100-500K LoC) System graph score 43 (higher by 31)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 16 hours ago · v2 · 128 actionable findings from 2 signal sources. 48 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 85.0 0.15 12.75
security_score 100.0 0.25 25.00
testing_score 32.0 0.20 6.40
documentation_score 62.0 0.15 9.30
practices_score 82.0 0.15 12.30
code_quality 80.0 0.10 8.00
Overall 1.00 73.8
security_score may be inflated — optional security scanners were skipped on this fast scan
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 11 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/`.
11 matching findings on this repo
  • info Commented-code block (7 lines) in _datafiles/html/admin/static/js/ansi-composer…
  • info Commented-code block (6 lines) in _datafiles/html/admin/static/js/script-wizard…
  • info Commented-code block (11 lines) in _datafiles/html/admin/static/js/picker.js:6
  • info Commented-code block (7 lines) in _datafiles/html/admin/static/js/select-dialog…
  • info Commented-code block (5 lines) in _datafiles/html/admin/static/js/script-editor…
  • info Commented-code block (8 lines) in _datafiles/html/admin/static/js/picker-config…
  • info Commented-code block (5 lines) in _datafiles/html/admin/static/js/mapper/mapper…
  • info Commented-code block (6 lines) in _datafiles/html/public/static/js/webclient-co…
  • info Commented-code block (5 lines) in _datafiles/html/public/static/js/triggers.js:6
  • info Commented-code block (7 lines) in _datafiles/html/public/static/js/fx.js:56
  • info Commented-code block (5 lines) in _datafiles/html/public/static/js/windows/wind…
View all commented-out code findings →
Config drift 3 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.
3 matching findings on this repo
  • info Commented-code block (8 lines) in _datafiles/html/admin/static/js/picker-config…
  • low Unused endpoint: GET /admin/api/v1/config
  • low Unused endpoint: PATCH /admin/api/v1/config
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/63642899-838f-4db3-a169-ca87d89f1d50/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/63642899-838f-4db3-a169-ca87d89f1d50/

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.