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.

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 55.76s for a 179.7 MB repo slow.
Repobility's analysis ran in 32.95s after the clone landed.

vm0-ai/vm0

https://github.com/vm0-ai/vm0 · scanned 2026-06-16 00:55 UTC (2 months, 1 week ago) · 10 languages

2412 raw signals (261 security + 2151 graph) 6th percentile · Typescript · huge (>500K LoC)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v3 · last Δ -9.7 (diff) · 749 actionable findings from 2 signal sources. 229 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 657 findings

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`	100.0	0.20	20.00
`documentation_score`	98.0	0.15	14.70
`practices_score`	82.0	0.15	12.30
`code_quality`	51.0	0.10	5.10
Overall		1.00	83.1

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 16 High 15 Medium 182 Low 298 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 92 System graph 657 Crowd 0 Layer: Quality 395 Security 65 Software 20 Cicd 10 Api 1 Frontend 251 Network 3 Hardware 4

Exclude dismissed / FP Exclude test files

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.

Duplicates & near-duplicates 2 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

2 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 4 places

View all duplicates & near-duplicates findings →

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

2 matching findings on this repo

low Old/deprecated-named symbol `user_legacy` in turbo/apps/api/src/signals/auth/__…
low Old/deprecated-named symbol `withoutLegacy` in turbo/packages/core/src/instruct…

View all legacy markers findings →

Commented-out code 92 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 (7 lines) in crates/runner/mitm-addon/tests/test_utils.py:…
info Commented-code block (6 lines) in crates/runner/mitm-addon/tests/test_x_billing…
info Commented-code block (6 lines) in crates/runner/mitm-addon/src/auth.py:163
info Commented-code block (11 lines) in crates/runner/mitm-addon/src/matching.py:1295
info Commented-code block (11 lines) in crates/runner/mitm-addon/src/mitm_addon.py:34
info Commented-code block (9 lines) in crates/runner/mitm-addon/src/usage/counters.p…
info Commented-code block (6 lines) in crates/runner/mitm-addon/src/usage/webhook.py…
info Commented-code block (7 lines) in crates/runner/mitm-addon/src/usage/providers/…
info Commented-code block (6 lines) in crates/runner/mitm-addon/src/usage/providers/…
info Commented-code block (5 lines) in crates/runner/mitm-addon/src/usage/providers/…
info Commented-code block (5 lines) in turbo/apps/api/eslint.config.mjs:70
info Commented-code block (5 lines) in turbo/apps/api/src/index.ts:4

View all commented-out code findings →

Config drift 11 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.

11 matching findings on this repo

high [MINED106] Phantom test coverage: test_rejects_invalid_scalar_field_config_valu… crates/runner/mitm-addon/tests/test_json_selectiv…:100
high [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers c… turbo/apps/platform/src/signals/zero-page/clipboa…:191
low Stray `console.log` in TS/JS — turbo/apps/cli/tsup.config.ts:52
medium Insecure pattern 'node_child_process' in turbo/apps/cli/tsup.config.ts:3 turbo/apps/cli/tsup.config.ts:3
low Node manifest has dependencies but no lockfile: turbo/packages/eslint-config/pa… turbo/packages/eslint-config/package.json
medium Runtime service client appears to use placeholder configuration
info Commented-code block (5 lines) in turbo/apps/api/eslint.config.mjs:70
info Commented-code block (7 lines) in turbo/apps/cli/tsup.config.ts:30
info Commented-code block (6 lines) in turbo/apps/platform/eslint.config.js:219
info Commented-code block (5 lines) in turbo/apps/web/next.config.js:8
info Commented-code block (5 lines) in turbo/apps/web/vitest.config.ts:12

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/c5e1fbe1-170b-4f36-b3c5-d92f53e41551/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/c5e1fbe1-170b-4f36-b3c5-d92f53e41551/

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.