hi-godot/godot-ai

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.

https://github.com/hi-godot/godot-ai · scanned 2026-05-16 13:30 UTC (1 day, 6 hours ago) · 10 languages

48 findings (1 legacy + 47 scanner) 99th percentile · Python · medium (20-100K LoC) Scanner says 91 (lower by 4)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 days, 5 hours ago · v1 · 48 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

{# ── 2026-05-17 R27 #5: score breakdown panel ────────────────────── Surfaces the score_breakdown JSON that's been silently stored on Repository for months. Turns hidden math into a trust signal. #}

Score breakdown â 2026-05-17-v4 calibration-aware

Component	Sub-score	Weight	Contribution
`structure_score`	100.0	0.15	15.00
`security_score`	99.0	0.25	24.75
`testing_score`	100.0	0.20	20.00
`documentation_score`	73.0	0.15	10.95
`practices_score`	65.0	0.15	9.75
`code_quality`	69.0	0.10	6.90
Overall		1.00	87.3

Calibrated penalty buckets (security_score): agent: 1.1

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.

Legacy markers 5 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.

5 matching findings on this repo

low Legacy-named symbol `plugin_old` in tests/integration/test_websocket.py:511
low Legacy-named symbol `main_copy` in tests/integration/test_mcp_tools.py:230
low Legacy-named symbol `update_backup` in tests/unit/test_editor_state_mixed_state…
low Legacy-named symbol `player_backup` in tests/unit/test_telemetry_decorator.py:82
low Legacy-named symbol `update_backup` in tests/unit/test_audit_data_loss_safeguar…

View all legacy markers findings →

Commented-out code 6 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/`.

6 matching findings on this repo

info Commented-code block (6 lines) in tests/integration/test_mcp_tools.py:3317
info Commented-code block (12 lines) in tests/integration/_self_update_fixture.py:237
info Commented-code block (5 lines) in tests/unit/test_editor_focus_refocus.py:647
info Commented-code block (5 lines) in tests/unit/test_dock_cli_timeout.py:120
info Commented-code block (5 lines) in src/godot_ai/handlers/_readiness.py:21
info Commented-code block (5 lines) in src/godot_ai/handlers/node.py:10

View all commented-out code findings →

{# ── 2026-05-17 Round 14: AI-agent bridge footer ────────────────────── Discoverability: the /agents/voting/ guide + MCP manifest exist but aren't linked from anywhere users actually land. Small, opt-in footer. #}

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/9524e016-8ff7-4315-a52d-06ff947101d1/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/9524e016-8ff7-4315-a52d-06ff947101d1/

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.