notque/vexjoy-agent

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.

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

Scan timing: clone 11.01s · analysis 21.38s · 22.7 MB · GitHub API rate-limit (preflight)

https://github.com/notque/vexjoy-agent · scanned 2026-06-05 20:54 UTC (4 days, 13 hours ago) · 10 languages

654 raw signals (210 security + 444 graph) 23rd percentile · Python · large (100-500K LoC) System graph score 80 (lower by 15)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 13 hours ago · v2 · 291 actionable findings from 2 signal sources. 141 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 · 203 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	25.4	0.25	6.35
`testing_score`	100.0	0.20	20.00
`documentation_score`	100.0	0.15	15.00
`practices_score`	80.0	0.15	12.00
`code_quality`	32.7	0.10	3.27
Overall		1.00	65.6

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 7 High 14 Medium 37 Low 134 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 88 System graph 203 Crowd 0 Layer: Quality 219 Software 51 Security 16 Cicd 3 Api 1 Frontend 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.

Duplicates & near-duplicates 3 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.

3 matching findings on this repo

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

View all duplicates & near-duplicates findings →

Commented-out code 48 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 scripts/pre-route.py:81
info Commented-code block (5 lines) in scripts/detect-workflow-capability.py:77
info Commented-code block (6 lines) in scripts/audit-skill-content.py:186
info Commented-code block (5 lines) in scripts/security-review-scan.py:237
info Commented-code block (7 lines) in scripts/feature-state.py:132
info Commented-code block (7 lines) in scripts/validate-workflow-conformance.py:108
info Commented-code block (5 lines) in scripts/check-skill-verdicts.py:166
info Commented-code block (7 lines) in scripts/strip-phantom-name-frontmatter.py:96
info Commented-code block (5 lines) in scripts/generate-skill-index.py:257
info Commented-code block (6 lines) in scripts/validate-hook-health.py:196
info Commented-code block (10 lines) in scripts/tests/test_index_router.py:600
info Commented-code block (5 lines) in scripts/tests/test_review_output_gate.py:155

View all commented-out code findings →

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

2 matching findings on this repo

low File has no detected symbols: plugins/custom-panel/rsbuild.config.ts
low Old/deprecated-named symbol `learning_db_v2` in hooks/pretool-config-protection…

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/a78d3324-e810-4b9e-bc21-cc4ea301f6aa/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a78d3324-e810-4b9e-bc21-cc4ea301f6aa/

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.