kzahel/yepanywhere

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.

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

Scan timing: clone 9.35s · analysis 54.59s · 22.1 MB · GitHub API rate-limit (preflight)

https://github.com/kzahel/yepanywhere · scanned 2026-06-05 19:09 UTC (4 days, 17 hours ago) · 10 languages

1222 raw signals (410 security + 812 graph) 10th percentile · Typescript · large (100-500K LoC) System graph score 50 (higher by 11)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 17 hours ago · v2 · 640 actionable findings from 2 signal sources. 176 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 · 357 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	24.4	0.25	6.10
`testing_score`	95.0	0.20	19.00
`documentation_score`	70.7	0.15	10.61
`practices_score`	89.0	0.15	13.35
`code_quality`	36.0	0.10	3.60
Overall		1.00	61.7

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 6 High 220 Medium 117 Low 238 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 283 System graph 357 Crowd 0 Layer: Quality 138 Software 254 Cicd 11 Security 24 Frontend 101 Network 2 Hardware 2 Api 108

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.

Commented-out code 22 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 scripts/find-unused-css.ts:214
info Commented-code block (5 lines) in packages/client/src/components/Sidebar.tsx:456
info Commented-code block (5 lines) in packages/client/src/components/MessageInput.t…
info Commented-code block (5 lines) in packages/client/src/components/renderers/tool…
info Commented-code block (7 lines) in packages/client/src/contexts/InboxContext.tsx…
info Commented-code block (6 lines) in packages/client/src/lib/mergeMessages.ts:144
info Commented-code block (5 lines) in packages/client/src/pages/SessionPage.tsx:2972
info Commented-code block (5 lines) in packages/client/src/hooks/useSessionStatuses.…
info Commented-code block (7 lines) in packages/client/src/hooks/useSession.ts:900
info Commented-code block (5 lines) in packages/client/src/hooks/useEngagementTracki…
info Commented-code block (5 lines) in packages/client/e2e/relay-integration.spec.ts…
info Commented-code block (5 lines) in packages/server/test/sessions/reader.test.ts:…

View all commented-out code findings →

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

5 matching findings on this repo

high Express POST /configure has no auth packages/server/src/remote-access/routes.ts:46
low File has no detected symbols: packages/client/playwright.config.ts
low File has no detected symbols: packages/client/vitest.config.ts
low Unused endpoint: GET /config
low Unused endpoint: POST /configure

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/eda2b2c7-9bb0-4fd6-b7c0-98d81de29a7a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/eda2b2c7-9bb0-4fd6-b7c0-98d81de29a7a/

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.