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.

pro-vi/designer

https://github.com/pro-vi/designer · scanned 2026-06-16 04:36 UTC (1 month, 3 weeks ago)

21 raw signals (0 security + 21 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 3 weeks ago · v1 · 21 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

66.7% cov · 21 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 1 Medium 7 Low 5 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 21 Crowd 0 Layer: Frontend 2 Security 5 Cicd 1 Quality 13

Exclude dismissed / FP Exclude test files

Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.

Scan summary Repository scanned at 75.9/100 with 66.7% coverage. It contains 154 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 21 findings — concentrated in quality (13), security (5), frontend (2). Risk profile is high: 0 critical, 1 high, 7 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 13 of 21 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph security security conf 1.00 Insecure pattern 'eval_used' in browser.ts:63

Found a known-risky pattern (eval_used). Review and replace if possible.

browser.ts:63 Eval used

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — designer-controller.ts:867

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data

A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.

Mock dataCritical flowGenerated repo pattern

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in cdp-ensure.ts:4

Found a known-risky pattern (node_child_process). Review and replace if possible.

cdp-ensure.ts:4 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in cross-platform.ts:3

Found a known-risky pattern (node_child_process). Review and replace if possible.

cross-platform.ts:3 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in setup.ts:4

Found a known-risky pattern (node_child_process). Review and replace if possible.

setup.ts:4 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in tasting.ts:3

Found a known-risky pattern (node_child_process). Review and replace if possible.

tasting.ts:3 Node child process

medium System graph quality Tests conf 1.00 Very low test-to-source ratio

0 test file(s) for 15 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.

Coverage

low System graph quality Production readiness conf 1.00 Composite production-readiness gap

Multiple low-cost hardening controls are missing together: ci, tests. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.

Repo hardeningGenerated repo pattern

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

Found 34 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.

CleanupRepo hardeningGenerated repo pattern

low System graph cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts

preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.

package.json CI/CD securitySupply chainNpm

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — cli.ts:53

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

Fq console leak

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — setup.ts:21

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

Fq console leak

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/0d4c3970-3e6a-480f-a13d-a8bc5e0ad862/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/0d4c3970-3e6a-480f-a13d-a8bc5e0ad862/

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.