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
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)

File as issue Image
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
Combined
64.7
/100
Security checks
86
36 findings
System graph
43
88.9% cov · 92 findings
Critical
6
click to filter
Agents
6
0 votes
Crowd
0
reported
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
Severity: Critical 6 High 5 Medium 43 Low 45 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 36 System graph 92 Crowd 0 Layer: Quality 42 Cicd 9 Security 8 Software 8 Frontend 5 Network 31 Hardware 4 Api 21

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Possible secret in internal/web/api_v1_users.go
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in internal/web/api_v1_users.go:92; move to env var / secrets manager.
internal/web/api_v1_users.go:92
#2
Possible secret in scripts/https-setup.sh
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in scripts/https-setup.sh:375; move to env var / secrets manager.
scripts/https-setup.sh:375
#3
Possible secret in cmd/reset-admin-pw/main.go
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in cmd/reset-admin-pw/main.go:83; move to env var / secrets manager.
cmd/reset-admin-pw/main.go:83
#4
Possible secret in cmd/reset-admin-pw/main.go
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in cmd/reset-admin-pw/main.go:90; move to env var / secrets manager.
cmd/reset-admin-pw/main.go:90
#5
Possible secret in _datafiles/world/default/localize/en.yaml
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in _datafiles/world/default/localize/en.yaml:10; move to env var / secrets manager.
_datafiles/world/default/localize/en.yaml:10
#6
Possible secret in _datafiles/world/empty/localize/en.yaml
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in _datafiles/world/empty/localize/en.yaml:10; move to env var / secrets manager.
_datafiles/world/empty/localize/en.yaml:10
#7
Privileged port 46 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in _datafiles/world/default/ansi-aliases.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
_datafiles/world/default/ansi-aliases.yaml
#8
Privileged port 90 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in _datafiles/world/default/ansi-aliases.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
_datafiles/world/default/ansi-aliases.yaml
#9
Privileged port 82 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in _datafiles/world/default/ansi-aliases.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
_datafiles/world/default/ansi-aliases.yaml
#10
Privileged port 118 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in _datafiles/world/default/ansi-aliases.yaml is a real port, change the binding to ≥1024 or run behind a proxy.
_datafiles/world/default/ansi-aliases.yaml

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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.