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.
67 of your 121 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 101.87s for a 208.3 MB repo slow.
  • Repobility's analysis ran in 17.74s after the clone landed.

EsotericSoftware/spine-runtimes

https://github.com/EsotericSoftware/spine-runtimes · scanned 2026-06-05 15:03 UTC (5 days, 2 hours ago) · 10 languages

418 raw signals (110 security + 308 graph) 11/13 scanners ran 43rd percentile · C · large (100-500K LoC) System graph score 84 (lower by 18)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 2 hours ago · v2 · 110 actionable findings from 2 signal sources. 154 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 40.0 0.15 6.00
security_score 100.0 0.25 25.00
testing_score 20.0 0.20 4.00
documentation_score 88.0 0.15 13.20
practices_score 67.0 0.15 10.05
code_quality 70.0 0.10 7.00
Overall 1.00 65.2
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 3 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/`.
3 matching findings on this repo
  • info Commented-code block (8 lines) in spine-ts/spine-webcomponents/src/SpineWebComp…
  • info Commented-code block (6 lines) in spine-ts/spine-webcomponents/src/SpineWebComp…
  • info Commented-code block (13 lines) in spine-ts/spine-core/src/BonePose.ts:424
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
  • low Possibly dead Python function: configure spine-godot/spine_godot/config.py:4
  • low File has no detected symbols: spine-ts/spine-threejs/example/react-three-fiber/…
  • low Stub function `configure` (body is just `pass`/`return`) — spine-godot/spine_go…
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/41c33865-a261-42d2-8b88-2b80c9044ccb/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/41c33865-a261-42d2-8b88-2b80c9044ccb/

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.