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.

youngtuck/everywhere-studio-beta

https://github.com/youngtuck/everywhere-studio-beta · scanned 2026-06-16 01:08 UTC (2 months, 1 week ago)

155 raw signals (0 security + 155 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 129 actionable findings from 1 signal source. 26 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 · 129 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 34 Medium 22 Low 29 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 129 Crowd 0 Layer: Frontend 17 Security 5 Cicd 1 Quality 67 Api 39

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 9 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.

9 matching findings on this repo

info TODO/FIXME marker in shipping code — legacy/api/kajabi-webhook.js:41
low Stray `console.log` in TS/JS — legacy/api/kajabi-webhook.js:39
low Stray `console.log` in TS/JS — legacy/api/adapt-format.js:325
low Stray `console.log` in TS/JS — legacy/api/generate.js:94
low Stray `console.log` in TS/JS — legacy/api/chat.js:405
low Stray `console.log` in TS/JS — legacy/api/run-pipeline.js:250
low Stray `console.log` in TS/JS — legacy/api/visual.js:134
medium `fetch()` without try/.catch or AbortSignal — legacy/api/visual.js:144
high Dangling fetch: POST https://api.firecrawl.dev/v1/search (legacy/api/chat.js:48…

View all legacy markers findings →

Commented-out code 41 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 (5 lines) in api/run-sentinel.js:63
info Commented-code block (7 lines) in api/adapt-format.js:240
info Commented-code block (6 lines) in api/validate-access-code.js:4
info Commented-code block (6 lines) in api/brand-dna-from-url.js:82
info Commented-code block (7 lines) in api/ingest-url.js:13
info Commented-code block (5 lines) in api/chat.js:469
info Commented-code block (6 lines) in api/watch-council-conversation.ts:5
info Commented-code block (8 lines) in api/watch-council-answer.ts:13
info Commented-code block (5 lines) in api/feedback.ts:6
info Commented-code block (5 lines) in src/utils/voiceDNAProcessor.ts:115
info Commented-code block (8 lines) in src/components/Logo.tsx:109
info Commented-code block (5 lines) in src/components/review/HumanVoiceVerdict.tsx:5

View all commented-out code 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/e9dd4831-c6e8-4b87-ad13-561b085be6e2/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e9dd4831-c6e8-4b87-ad13-561b085be6e2/

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.