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.

RevealUIStudio/revealui

https://github.com/RevealUIStudio/revealui · scanned 2026-06-15 23:51 UTC (2 months, 3 weeks ago)

1606 raw signals (0 security + 1606 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 1584 actionable findings from 1 signal source. 22 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 · 1584 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 20 High 983 Medium 160 Low 233 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 1584 Crowd 0 Layer: Frontend 153 Network 2 Hardware 5 Security 97 Cicd 3 Quality 302 Api 1022

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 `cus_legacy` in apps/server/src/lib/__tests__/billi…
low Old/deprecated-named symbol `cus_legacy` in packages/core/src/__tests__/license…
low Old/deprecated-named symbol `agt_legacy` in packages/contracts/src/__tests__/ag…

View all legacy markers findings →

Commented-out code 157 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 apps/docs/vitest.config.ts:22
info Commented-code block (6 lines) in apps/docs/scripts/prune-non-public.mjs:5
info Commented-code block (5 lines) in apps/docs/scripts/served-docs.mjs:3
info Commented-code block (5 lines) in apps/docs/app/App.tsx:90
info Commented-code block (5 lines) in apps/docs/app/utils/markdown.tsx:95
info Commented-code block (5 lines) in apps/marketing/app/__tests__/agency-engagemen…
info Commented-code block (9 lines) in apps/marketing/app/components/landing/Fork.ts…
info Commented-code block (8 lines) in apps/marketing/app/content/primitives.ts:1
info Commented-code block (8 lines) in apps/marketing/app/content/for-operators-how-…
info Commented-code block (5 lines) in apps/marketing/app/content/persona.ts:1
info Commented-code block (5 lines) in apps/marketing/app/content/marketplace.ts:1
info Commented-code block (8 lines) in apps/marketing/app/content/products.ts:3

View all commented-out code findings →

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

12 matching findings on this repo

low Stray `console.log` in TS/JS — apps/docs/vite.config.ts:108
low Stray `console.log` in TS/JS — packages/contracts/src/__tests__/integration-rea…
low Node manifest has dependencies but no lockfile: packages/config/package.json packages/config/package.json
medium Runtime service client appears to use placeholder configuration
high Agent instruction/config may expose a secret: CLAUDE.md CLAUDE.md:231
info Commented-code block (6 lines) in apps/docs/vitest.config.ts:22
info Commented-code block (6 lines) in apps/admin/tailwind.config.ts:12
info Commented-code block (5 lines) in apps/admin/revealui.config.ts:40
info Commented-code block (5 lines) in apps/admin/next.config.mjs:88
info Commented-code block (5 lines) in apps/admin/vitest.config.ts:33
info Commented-code block (7 lines) in apps/server/tsup.config.ts:20
info Commented-code block (6 lines) in apps/server/vitest.config.ts:8

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/59fd59aa-6060-4bfb-a318-ffd6b60ef66d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/59fd59aa-6060-4bfb-a318-ffd6b60ef66d/

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.