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.

althaqelco/uneom.com

https://github.com/althaqelco/uneom.com · scanned 2026-06-17 01:32 UTC (1 month, 2 weeks ago)

26 raw signals (0 security + 26 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

55.6% cov · 26 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 1 Medium 17 Low 4 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 26 Crowd 0 Layer: Frontend 6 Security 10 Quality 10

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 95.0/100 with 55.6% coverage. It contains 647 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 26 findings — concentrated in security (10), quality (10), frontend (6). Risk profile is high: 0 critical, 1 high, 17 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 22 of 26 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 scripts/split-images-registry.mjs:45

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

scripts/split-images-registry.mjs:45 Eval used

medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/app/layout.tsx:107

Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html

Fq dangerous html

medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/components/ui/ResponsiveImage.tsx:62

Fq dangerous html

medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/components/WebMCPProvider.tsx:107

Fq dangerous html

medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/lib/seo/JsonLd.tsx:17

Fq dangerous html

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

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

Repo hardeningGenerated repo pattern

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 'dangerous_innerhtml' in src/app/layout.tsx:107

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

src/app/layout.tsx:107 Dangerous innerhtml

medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/components/ui/ResponsiveImage.tsx:62

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

src/components/ui/ResponsiveImage.tsx:62 Dangerous innerhtml

medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/components/WebMCPProvider.tsx:107

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

src/components/WebMCPProvider.tsx:107 Dangerous innerhtml

medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/lib/seo/JsonLd.tsx:17

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

src/lib/seo/JsonLd.tsx:17 Dangerous innerhtml

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/c2pa/sign-all.mjs:22

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

scripts/c2pa/sign-all.mjs:22 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/fix-dates.mjs:8

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

scripts/fix-dates.mjs:8 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/fix-metadata.mjs:8

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

scripts/fix-metadata.mjs:8 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/process-images.mjs:25

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

scripts/process-images.mjs:25 Node child process

medium System graph security Coverage conf 1.00 No auth library detected

The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.

auth

medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 17 placeholder/mock markers across 6 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.

Mock dataIncompleteGenerated repo pattern

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

1 test file(s) for 107 source file(s) (ratio 0.01). Consider adding integration or unit tests for critical paths.

Coverage

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

Found 49 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 quality License conf 1.00 No license file detected

No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.

Repo hardeningGenerated repo pattern

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `blogDeprecated` in next.config.mjs:201

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/app/api/quote/route.ts:47

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/4f4c86d8-ce9c-4e1a-8be7-90993e841019/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/4f4c86d8-ce9c-4e1a-8be7-90993e841019/

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.