build23w/fdv.lol

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.

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

Scan timing: clone 4.75s · analysis 5.48s · 9.4 MB · GitHub API rate-limit (preflight)

https://github.com/build23w/fdv.lol · scanned 2026-06-06 00:58 UTC (4 days, 1 hour ago) · 10 languages

283 raw signals (75 security + 208 graph) 13th percentile · Javascript · medium (20-100K LoC) System graph score 83 (lower by 33)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 1 hour ago · v2 · 133 actionable findings from 2 signal sources. 46 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

77.8% cov · 104 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	65.0	0.15	9.75
`security_score`	53.4	0.25	13.35
`testing_score`	20.0	0.20	4.00
`documentation_score`	58.5	0.15	8.78
`practices_score`	65.0	0.15	9.75
`code_quality`	43.7	0.10	4.37
Overall		1.00	50.0

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 6 Medium 18 Low 80 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 29 System graph 104 Crowd 0 Layer: Quality 84 Software 24 Security 3 Cicd 2 Api 1 Frontend 19

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 `asLegacy` in src/vista/addons/auto/lib/dex.js:1400

View all legacy markers findings →

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

9 matching findings on this repo

info Commented-code block (5 lines) in src/analytics/shill.js:364
info Commented-code block (9 lines) in src/agents/driver.js:1781
info Commented-code block (11 lines) in src/agents/frameworks/deepseek.js:206
info Commented-code block (7 lines) in src/core/tools.js:114
info Commented-code block (10 lines) in src/vista/addons/auto/lib/sell/more.js:1
info Commented-code block (7 lines) in src/vista/addons/auto/trader/index.js:904
info Commented-code block (7 lines) in src/vista/addons/auto/volume/index.js:91
info Commented-code block (14 lines) in src/vista/profile/parts/hero.js:140
info Commented-code block (7 lines) in src/vista/meme/page.js:120

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: src/agents/personas/strategies/agent.gary.config.…
low Old/deprecated-named symbol `fdv_gary_training_captures_v1` in src/config/env.j…

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/92da7b85-38fd-4b5f-b903-da4bade9d842/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/92da7b85-38fd-4b5f-b903-da4bade9d842/

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.