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.

vdekrijger/review123

https://github.com/vdekrijger/review123 · scanned 2026-06-16 00:47 UTC (2 months, 1 week ago)

205 raw signals (109 security + 96 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 103 actionable findings from 2 signal sources. 444 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 96 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 2 Medium 20 Low 17 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 7 System graph 96 Crowd 0 Layer: Quality 88 Security 8 Api 1 Frontend 3 Network 2 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 3 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.

3 matching findings on this repo

low Old/deprecated-named symbol `mLegacy` in src/lib/router/router.svelte.ts:61
low Old/deprecated-named symbol `ghp_legacy` in src/lib/github/client.test.ts:37
low Old/deprecated-named symbol `idbDeleteLegacy` in src/lib/drafts/drafts.svelte.t…

View all legacy markers findings →

Commented-out code 58 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 vite.config.ts:41
info Commented-code block (8 lines) in src/test-setup.ts:3
info Commented-code block (10 lines) in src/App.test.ts:18
info Commented-code block (7 lines) in src/vite-env.d.ts:11
info Commented-code block (5 lines) in src/components/InspectStep.tree.test.ts:314
info Commented-code block (5 lines) in src/components/InspectStep.skills.test.ts:313
info Commented-code block (6 lines) in src/components/CommentEditor.test.ts:338
info Commented-code block (5 lines) in src/components/InspectStep.test.ts:176
info Commented-code block (5 lines) in src/components/UnderstandStep.test.ts:883
info Commented-code block (5 lines) in src/components/InspectStep.draft-visibility.t…
info Commented-code block (5 lines) in src/components/InspectStep.drawer-left.test.t…
info Commented-code block (5 lines) in src/components/ContextRail.test.ts:484

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

medium Insecure pattern 'node_child_process' in vite.config.ts:2 vite.config.ts:2
info Commented-code block (9 lines) in vite.config.ts:41

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/fc92597e-ce6e-4e9c-8bb2-ab0c9967ce04/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/fc92597e-ce6e-4e9c-8bb2-ab0c9967ce04/

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.