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
58 of your 107 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 48.18s for a 84.1 MB repo slow.
  • Repobility's analysis ran in 32.55s after the clone landed.

opentoonz/opentoonz

https://github.com/opentoonz/opentoonz.git · scanned 2026-05-20 21:40 UTC (2 weeks, 1 day ago) · 10 languages

388 findings (100 legacy + 288 scanner) 11/13 scanners ran Scanner says 73 (lower by 11)

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

Complete repo analysis

Last scanned 2 weeks, 1 day ago · v3 · 296 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
70.4
/100
Repobility
67
200 legacy
9-layer
73
88.9% cov · 96 gaps
Critical
7
click to filter
Agents
6
0 votes
Crowd
0
reported
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 15.0 0.20 3.00
documentation_score 75.0 0.15 11.25
practices_score 67.0 0.15 10.05
code_quality 70.0 0.10 7.00
Overall 1.00 62.3
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 7 High 140 Medium 6 Low 101 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 200 9-layer 96 Crowd 0 Layer: Quality 155 Security 9 Software 126 Api 1 Network 1 Frontend 1 Cicd 3

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 119 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 [MINED111] Bare except continues silently: Bare `except:` (or `except Exception… toonz/sources/toonz/toonz_qrc_validator.py:53
  • medium [MINED111] Bare except continues silently: Bare `except:` (or `except Exception… toonz/sources/toonz/toonz_qrc_validator.py:53
  • medium [COMP001] High cognitive complexity: Function `print_report` has cognitive comp… toonz/sources/toonz/toonz_qrc_validator.py:83
  • medium [COMP001] High cognitive complexity: Function `print_report` has cognitive comp… toonz/sources/toonz/toonz_qrc_validator.py:83
  • low Duplicated implementation block across source files thirdparty/kiss_fft/tools/psdpng.c:34
  • low Duplicated implementation block across source files thirdparty/kiss_fft/tools/psdpng.c:34
  • low Duplicated implementation block across source files thirdparty/glew/glew-1.9.0/include/GL/glxew.h:1
  • low Duplicated implementation block across source files thirdparty/glew/glew-1.9.0/include/GL/glxew.h:1
  • low Duplicated implementation block across source files thirdparty/glew/glew-1.9.0/auto/src/glew_utils.c:14
  • low Duplicated implementation block across source files thirdparty/glew/glew-1.9.0/auto/src/glew_utils.c:14
  • low Duplicated implementation block across source files thirdparty/Lz4/Lz4_131/programs/lz4io.h:8
  • low Duplicated implementation block across source files thirdparty/Lz4/Lz4_131/programs/lz4io.h:8
View all fragile runtime findings →
Config drift 1 finding
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.
1 matching finding on this repo
  • low Very large file: thirdparty/tiff-4.0.3/config/ltmain.sh (9655 lines)
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/895158db-3965-47f3-ab73-ba9a1a655881/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/895158db-3965-47f3-ab73-ba9a1a655881/

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.