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

Scan timing: clone 21.7s · analysis 14.02s · 80.3 MB · GitHub API rate-limit (preflight)

modu-ai/moai-adk

https://github.com/modu-ai/moai-adk · scanned 2026-05-31 01:24 UTC (5 days, 7 hours ago) · 10 languages

265 findings (90 legacy + 175 scanner) 11/13 scanners ran 67th percentile · Go · large (100-500K LoC) Scanner says 77 (higher by 11)

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

Complete repo analysis

Last scanned 5 days, 7 hours ago · v2 · 194 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
83.9
/100
Repobility
91
90 legacy
9-layer
77
100.0% cov · 104 gaps
Critical
8
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 85.0 0.20 17.00
documentation_score 90.0 0.15 13.50
practices_score 84.0 0.15 12.60
code_quality 70.0 0.10 7.00
Overall 1.00 87.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 8 High 55 Medium 27 Low 77 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 90 9-layer 104 Crowd 0 Layer: Security 26 Quality 56 Software 51 Api 1 Frontend 13 Network 2 Cicd 45

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.

Fragile runtime 46 findings
What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.
Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.
How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.
Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).
12 matching findings on this repo
  • medium [SEC123] Production stack trace / debug output exposed: Debug mode left on in p… internal/hook/security/rules.go:208
  • medium [SEC087] JS: weak Math.random for crypto: Math.random() is not cryptographicall… .moai/brain/IDEA-002/claude-design-handoff/projec…:152
  • medium localStorage write failures are swallowed silently .moai/design/SPEC-V3R3-CLI-TUI-001/source/project…:270
  • low Duplicated implementation block across source files internal/harness/tier/tier.go:7
  • low Duplicated implementation block across source files .moai/scripts/status-drift-cleanup.go:110
  • low [ERR003] Ignored Error (Go): Ignoring error return values. internal/cli/astgrep.go:130
  • low [ERR003] Ignored Error (Go): Ignoring error return values. internal/ciwatch/state.go:57
  • low [ERR003] Ignored Error (Go): Ignoring error return values. internal/astgrep/rules.go:36
  • low Duplicated implementation block across source files internal/lsp/hook/tracker.go:123
  • low Duplicated implementation block across source files internal/lsp/aggregator/aggregator.go:173
  • low Duplicated implementation block across source files internal/loop/storage.go:68
  • low Duplicated implementation block across source files internal/hook/user_prompt_submit.go:69
View all fragile runtime findings →
Legacy markers 2 findings
What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.
Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.
How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.
Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.
2 matching findings on this repo
  • low Legacy-named symbol `gdoc_copy` in docs-site/themes/hugo-geekdoc/static/js/main…
  • low Legacy-named symbol `AsOld` in docs-site/themes/hugo-geekdoc/static/js/8731-02f…
View all legacy markers 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/b17cb6f7-f398-498c-b7bc-c52164018838/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/b17cb6f7-f398-498c-b7bc-c52164018838/

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.