ubugeeei-prod/vize

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.

41 of your 120 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 13.53s · analysis 20.13s · 63.2 MB · GitHub API rate-limit (preflight)

https://github.com/ubugeeei-prod/vize · scanned 2026-06-05 18:27 UTC (4 days, 19 hours ago) · 10 languages

476 raw signals (100 security + 376 graph) 11/13 scanners ran 92nd percentile · Rust · large (100-500K LoC)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 19 hours ago · v2 · 229 actionable findings from 2 signal sources. 59 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 · 186 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	100.0	0.25	25.00
`testing_score`	76.0	0.20	15.20
`documentation_score`	96.0	0.15	14.40
`practices_score`	86.0	0.15	12.90
`code_quality`	70.0	0.10	7.00
Overall		1.00	83.5

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 0 High 4 Medium 14 Low 175 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 43 System graph 186 Crowd 0 Layer: Quality 57 Software 53 Security 3 Api 1 Frontend 109 Network 5 Cicd 1

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.

Legacy markers 1 finding

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.

1 matching finding on this repo

low Old/deprecated-named symbol `generateOutputLegacy` in npm/vite-plugin-vize/src/…

View all legacy markers findings →

Commented-out code 6 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/`.

6 matching findings on this repo

info Commented-code block (5 lines) in tests/tooling/github-workflows.test.ts:51
info Commented-code block (6 lines) in tests/snapshots/check/ant-design-vue.ts:46
info Commented-code block (5 lines) in npm/nuxt/src/index.ts:342
info Commented-code block (9 lines) in npm/vite-plugin-vize/example/vize.config.ts:52
info Commented-code block (6 lines) in npm/vite-plugin-vize/src/plugin/resolve.ts:554
info Commented-code block (8 lines) in tools/vite-plus/tasks/build.ts:33

View all commented-out code findings →

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

10 matching findings on this repo

low File has no detected symbols: vite.config.ts
low File has no detected symbols: playground/playwright.config.ts
low File has no detected symbols: playground/vite.config.ts
low File has no detected symbols: playground/vite.test.config.ts
low File has no detected symbols: playground/vite.app.config.ts
low File has no detected symbols: playground/vite.node.config.ts
low File has no detected symbols: tests/app/playwright.config.ts
low File has no detected symbols: tests/app/playwright.vrt.config.ts
low Very large file: crates/vize/src/commands/check/tsconfig_inputs.rs (1678 lines)
info Commented-code block (9 lines) in npm/vite-plugin-vize/example/vize.config.ts:52

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/838df817-0857-4287-990d-e32b2463fcfc/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/838df817-0857-4287-990d-e32b2463fcfc/

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.