YunYouJun/valaxy

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.

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

Scan timing: clone 2.68s · analysis 85.11s · 3.1 MB · GitHub preflight 548ms

https://github.com/YunYouJun/valaxy · scanned 2026-06-05 19:26 UTC (4 days, 16 hours ago) · 10 languages

436 raw signals (192 security + 244 graph) 5th percentile · Typescript · medium (20-100K LoC) System graph score 58 (lower by 9)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 16 hours ago · v2 · 225 actionable findings from 2 signal sources. 89 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 · 110 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	11.6	0.25	2.90
`testing_score`	46.0	0.20	9.20
`documentation_score`	63.0	0.15	9.45
`practices_score`	69.0	0.15	10.35
`code_quality`	71.6	0.10	7.16
Overall		1.00	48.1

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 6 High 46 Medium 49 Low 87 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 115 System graph 110 Crowd 0 Layer: Software 141 Cicd 9 Security 11 Quality 35 Frontend 24 Hardware 4 Api 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 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 `ssgBuildLegacy` in packages/valaxy/node/build.ts:89
low Old/deprecated-named symbol `ssgBuildLegacy` in packages/valaxy/node/cli/build.…

View all legacy markers findings →

Commented-out code 17 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 (6 lines) in demo/yun/valaxy.config.ts:97
info Commented-code block (6 lines) in demo/yun/setup/main.ts:5
info Commented-code block (7 lines) in test/create-valaxy.test.ts:28
info Commented-code block (6 lines) in test/addon.test.ts:77
info Commented-code block (7 lines) in packages/valaxy-theme-yun/types/index.d.ts:116
info Commented-code block (5 lines) in packages/valaxy/node/options.ts:82
info Commented-code block (6 lines) in packages/valaxy/node/cli/utils/shortcuts.ts:70
info Commented-code block (6 lines) in packages/valaxy/node/plugins/unocss.ts:100
info Commented-code block (6 lines) in packages/valaxy/node/plugins/preset.ts:135
info Commented-code block (6 lines) in packages/valaxy/node/plugins/extendConfig.ts:…
info Commented-code block (7 lines) in packages/valaxy/node/plugins/vueRouter.ts:192
info Commented-code block (6 lines) in packages/valaxy/node/plugins/valaxy/index.ts:…

View all commented-out code findings →

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

12 matching findings on this repo

low File has no detected symbols: playwright.config.ts
low File has no detected symbols: eslint.config.js
low File has no detected symbols: uno.config.ts
low File has no detected symbols: vitest.config.ts
low File has no detected symbols: demo/custom/valaxy.config.ts
low File has no detected symbols: demo/custom/site.config.ts
low File has no detected symbols: demo/custom/valaxy-theme-custom/valaxy.config.ts
low File has no detected symbols: demo/yun/valaxy.config.ts
low File has no detected symbols: demo/yun/vite.config.ts
low File has no detected symbols: demo/yun/theme.config.ts
low File has no detected symbols: demo/yun/site.config.ts
low File has no detected symbols: test/fixtures/user/valaxy.config.ts

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/eaadfe9b-d3bc-4c8a-9ba7-80ffc334d7d7/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/eaadfe9b-d3bc-4c8a-9ba7-80ffc334d7d7/

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.