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
48 of your 90 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 16.11s · analysis 13.15s · 44.1 MB · GitHub API rate-limit (preflight)

apache/echarts

https://github.com/apache/echarts · scanned 2026-06-05 08:45 UTC (5 days, 20 hours ago) · 10 languages

902 raw signals (84 security + 818 graph) 11/13 scanners ran 80th percentile · Typescript · large (100-500K LoC) System graph score 90 (lower by 7)

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

Complete repo analysis

Last scanned 5 days, 20 hours ago · v2 · 417 actionable findings from 2 signal sources. 76 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
89.9
/100
Security checks
90
23 findings
System graph
90
88.9% cov · 394 findings
Critical
1
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 72.0 0.20 14.40
documentation_score 81.0 0.15 12.15
practices_score 82.0 0.15 12.30
code_quality 70.0 0.10 7.00
Overall 1.00 83.6
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 1 High 3 Medium 4 Low 103 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 23 System graph 394 Crowd 0 Layer: Quality 147 Security 5 Cicd 2 Software 53 Api 1 Frontend 209

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 4 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.
4 matching findings on this repo
  • low Old/deprecated-named symbol `roundLegacy` in src/util/number.ts:239
  • low Old/deprecated-named symbol `markupTextArrLegacy` in src/component/tooltip/Tool…
  • low Old/deprecated-named symbol `userIntervalUseLegacy` in src/coord/axisNiceTicks.…
  • low Old/deprecated-named symbol `roundLegacy` in src/export/api/number.ts:22
View all legacy markers findings →
Commented-out code 111 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/`.
12 matching findings on this repo
  • info Commented-code block (9 lines) in test/lib/testHelper.js:3202
  • info Commented-code block (6 lines) in test/lib/countup.js:8
  • info Commented-code block (6 lines) in test/lib/frameInsight.js:46
  • info Commented-code block (8 lines) in test/lib/canteen.js:559
  • info Commented-code block (5 lines) in test/ut/spec/util/number.test.ts:1067
  • info Commented-code block (11 lines) in test/ut/spec/api/getVisual.test.ts:162
  • info Commented-code block (11 lines) in test/ut/spec/api/containPixel.test.ts:323
  • info Commented-code block (6 lines) in test/ut/spec/component/graphic/setOption.test…
  • info Commented-code block (9 lines) in test/ut/core/utHelper.ts:93
  • info Commented-code block (10 lines) in test/runTest/client/client.js:1007
  • info Commented-code block (6 lines) in test/runTest/runtime/timeline.js:161
  • info Commented-code block (7 lines) in extension-src/bmap/BMapCoordSys.ts:147
View all commented-out code 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
  • high [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers c… extension-src/dataTool/gexf.ts:33
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/799907e4-3784-4afd-9be7-4713055c12df/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/799907e4-3784-4afd-9be7-4713055c12df/

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.