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.

tomi191/EuphoriaBeautyBar

https://github.com/tomi191/EuphoriaBeautyBar · scanned 2026-06-16 00:39 UTC (2 months, 1 week ago)

38 raw signals (0 security + 38 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 38 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 38 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 12 Low 10 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 38 Crowd 0 Layer: Api 1 Frontend 16 Security 2 Cicd 1 Quality 18

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 86.2/100 with 100.0% coverage. It contains 1048 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 38 findings — concentrated in quality (18), frontend (16), security (2). Risk profile is low: 0 critical, 0 high, 12 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

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

medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/components/seo/json-ld.tsx:15

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 quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/lib/blog-writer/cover-image.ts:79

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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/lib/blog-writer/inline-images.ts:111

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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/lib/blog-writer/openrouter.ts:43

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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/lib/google-oauth.ts:54

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 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/components/seo/json-ld.tsx:15

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

src/components/seo/json-ld.tsx:15 Dangerous innerhtml

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/montibello-scrape.ts:22

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

scripts/montibello-scrape.ts:22 Node child process

medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected

No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.

CI/CD securityCoverage

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

Found 64 placeholder/mock markers across 24 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

4 test file(s) for 244 source file(s) (ratio 0.02). Consider adding integration or unit tests for critical paths.

Coverage

low System graph quality Integrity conf 1.00 16 env vars used in code but missing from .env.example

Drift between code and config docs. The first few: `BLOG_OPENROUTER_MODEL`, `CRON_SECRET`, `DATABASE_URL_SESSION`, `GOOGLE_OAUTH_CLIENT_ID`, `GOOGLE_OAUTH_CLIENT_SECRET`, `GOOGLE_REVIEW_URL`, `KIE_AI_API_KEY`, `NEXT_PUBLIC_PASSKEYS_ENABLED` + 8 more. Add them (with a placeholder/comment) to .env.ex…

config drift

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

Found 38 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 Provenance conf 1.00 Shallow git history limits provenance confidence

The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.

Git historyGenerated repo pattern

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/check-parallel-logic.ts:10