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

Scan timing: clone 3.79s · analysis 32.32s · 6.2 MB · GitHub preflight 445ms

vuejs/core

https://github.com/vuejs/core · scanned 2026-06-05 11:06 UTC (5 days, 13 hours ago) · 10 languages

381 raw signals (79 security + 302 graph) 28th percentile · Typescript · large (100-500K LoC) System graph score 96 (lower by 27)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 13 hours ago · v2 · 208 actionable findings from 2 signal sources. 22 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 60.0 0.15 9.00
security_score 52.0 0.25 13.00
testing_score 95.0 0.20 19.00
documentation_score 70.7 0.15 10.61
practices_score 70.0 0.15 10.50
code_quality 68.1 0.10 6.81
Overall 1.00 68.9
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 34 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 (8 lines) in packages/server-renderer/__tests__/ssrCompute…
  • info Commented-code block (6 lines) in packages/server-renderer/src/render.ts:60
  • info Commented-code block (5 lines) in packages/compiler-core/__tests__/testUtils.ts…
  • info Commented-code block (5 lines) in packages/compiler-core/src/parser.ts:847
  • info Commented-code block (5 lines) in packages/compiler-core/src/babelUtils.ts:491
  • info Commented-code block (5 lines) in packages/compiler-core/src/codegen.ts:488
  • info Commented-code block (7 lines) in packages/compiler-core/src/transforms/vSlot.t…
  • info Commented-code block (5 lines) in packages/compiler-core/src/transforms/transfo…
  • info Commented-code block (6 lines) in packages/compiler-dom/src/transforms/transfor…
  • info Commented-code block (7 lines) in packages/compiler-dom/src/transforms/stringif…
  • info Commented-code block (8 lines) in packages/compiler-sfc/__tests__/compileTempla…
  • info Commented-code block (8 lines) in packages/compiler-sfc/__tests__/compileScript…
View all commented-out code findings →
Config drift 5 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.
5 matching findings on this repo
  • low File has no detected symbols: eslint.config.js
  • low File has no detected symbols: vitest.config.ts
  • low File has no detected symbols: packages/shared/src/domTagConfig.ts
  • low File has no detected symbols: packages/vue-compat/__tests__/globalConfig.spec.ts
  • low Stray `console.log` in TS/JS — rollup.config.js:127
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/1611bbb0-b505-443a-916f-0f14d01eae94/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/1611bbb0-b505-443a-916f-0f14d01eae94/

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.