codemedavid/TheWhatStage-v3 — Repobility public scan

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.

Sign up free Scan another repo

codemedavid/TheWhatStage-v3

https://github.com/codemedavid/TheWhatStage-v3 · scanned 2026-06-17 01:50 UTC (1 month, 1 week ago)

134 raw signals (0 security + 134 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ +8.6 (diff) · 134 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

Security checks

88.9% cov · 134 findings

click to filter

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 13 Low 41 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 134 Crowd 0 Layer: Api 1 Frontend 63 Quality 70

Exclude dismissed / FP Exclude test files

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1

Placeholder or mock-heavy implementation detected

GapSeverity.MEDIUM Layer.QUALITY score 0.225

Why: medium severity

#2

Critical user flow still appears backed by mock or placeholder data

GapSeverity.MEDIUM Layer.QUALITY score 0.225

Why: medium severity

#3

Agent instructions exist but release-hardening basics are missing

GapSeverity.MEDIUM Layer.QUALITY score 0.225

Why: medium severity

#4

`fetch()` without try/.catch or AbortSignal — src/app/api/webhooks/facebook/route.ts:174

GapSeverity.MEDIUM Layer.QUALITY score 0.225

Why: medium severity · crashes are likely without this

Fix: Wrap the `fetch(...)` in `try { ... } catch` in src/app/api/webhooks/facebook/route.ts:174, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.

#5

`fetch()` without try/.catch or AbortSignal — src/app/a/[slug]/_kinds/catalog/Renderer.tsx:103

GapSeverity.MEDIUM Layer.QUALITY score 0.225

Why: medium severity · crashes are likely without this

Fix: Wrap the `fetch(...)` in `try { ... } catch` in src/app/a/[slug]/_kinds/catalog/Renderer.tsx:103, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.

#6

`fetch()` without try/.catch or AbortSignal — src/app/(app)/dashboard/workflows/[id]/WorkflowEditor.tsx:587

GapSeverity.MEDIUM Layer.QUALITY score 0.225

Why: medium severity · crashes are likely without this

Fix: Wrap the `fetch(...)` in `try { ... } catch` in src/app/(app)/dashboard/workflows/[id]/WorkflowEditor.tsx:587, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.

#7

`fetch()` without try/.catch or AbortSignal — src/app/(app)/dashboard/workflows/_components/WorkflowsList.tsx:70

GapSeverity.MEDIUM Layer.QUALITY score 0.225

Why: medium severity · crashes are likely without this

Fix: Wrap the `fetch(...)` in `try { ... } catch` in src/app/(app)/dashboard/workflows/_components/WorkflowsList.tsx:70, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.

#8

`fetch()` without try/.catch or AbortSignal — src/app/(app)/dashboard/chatbot/_components/AutoFollowupForm.tsx:150

GapSeverity.MEDIUM Layer.QUALITY score 0.225

Why: medium severity · crashes are likely without this

Fix: Wrap the `fetch(...)` in `try { ... } catch` in src/app/(app)/dashboard/chatbot/_components/AutoFollowupForm.tsx:150, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.

#9

`fetch()` without try/.catch or AbortSignal — src/app/(app)/dashboard/chatbot/_components/MediaPickerModal.tsx:50

GapSeverity.MEDIUM Layer.QUALITY score 0.225

Why: medium severity · crashes are likely without this

Fix: Wrap the `fetch(...)` in `try { ... } catch` in src/app/(app)/dashboard/chatbot/_components/MediaPickerModal.tsx:50, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.

#10

`fetch()` without try/.catch or AbortSignal — src/app/(app)/dashboard/business/_components/ProductImageUpload.tsx:25

GapSeverity.MEDIUM Layer.QUALITY score 0.225

Why: medium severity · crashes are likely without this

Fix: Wrap the `fetch(...)` in `try { ... } catch` in src/app/(app)/dashboard/business/_components/ProductImageUpload.tsx:25, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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/2d1532e8-10b0-4216-8bd8-2b8c2ca63a7c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/2d1532e8-10b0-4216-8bd8-2b8c2ca63a7c/

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.