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.
Sign up free Scan another repo

uditmisra/wedding-seats-simplified

https://github.com/uditmisra/wedding-seats-simplified · scanned 2026-06-16 00:44 UTC (2 months, 1 week ago)

64 raw signals (0 security + 64 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
62.8
/100
Security checks
63
0 findings
System graph
63
77.8% cov · 59 findings
Critical
2
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 2 High 1 Medium 21 Low 11 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 59 Crowd 0 Layer: Frontend 26 Security 13 Cicd 1 Quality 19
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 62.8/100 with 77.8% coverage. It contains 905 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 64 findings — concentrated in frontend (26), quality (24), security (13). Risk profile is high: 2 critical, 1 high, 26 medium. Recommended next step: open the frontend layer findings first — that's where the highest-impact wins live.

Showing 35 of 59 actionable findings. 64 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical System graph security Secrets conf 1.00 Runtime dotenv file present in repo: .env
`.env` looks like a runtime dotenv file. It contains secret-looking assignments for VITE_SUPABASE_PUBLISHABLE_KEY. Move real values to a secret manager and keep only `.env.example` style templates in source control.
.env ConfigEnv fileRuntime env
critical System graph security Secrets conf 1.00 Runtime dotenv file present in repo: .env.production
`.env.production` looks like a runtime dotenv file. It contains secret-looking assignments for VITE_PAYMENTS_CLIENT_TOKEN. Move real values to a secret manager and keep only `.env.example` style templates in source control.
.env.production ConfigEnv fileRuntime env
high System graph security Secrets conf 1.00 Runtime dotenv file present in repo: .env.development
`.env.development` looks like a runtime dotenv file. No high-confidence secret value was matched, but runtime dotenv files often drift into live credentials. Move real values to a secret manager and keep only `.env.example` style templates in source control.
.env.development ConfigEnv fileRuntime env
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/components/ui/chart.tsx:70
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/pages/BlogPost.tsx:191
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 — supabase/functions/_shared/paddle.ts:35
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 — supabase/functions/ai-parse/index.ts:211
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 Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, ci, operator-readme. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, operator-readme. 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 quality Integrity conf 1.00 6 occurrences Frontend route `/reset-password` has no Link/navigate to it — src/App.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
6 occurrences
repo-level (6 hits)
Orphan pageWiring
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/admin-ops/index.ts:7
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/admin-ops/index.ts:7 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/ai-parse/index.ts:5
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/ai-parse/index.ts:5 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/auth-email-hook/index.ts:14
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/auth-email-hook/index.ts:14 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/consume-paddle-session/index.ts:4
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/consume-paddle-session/index.ts:4 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/get-paddle-price/index.ts:4
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/get-paddle-price/index.ts:4 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/handle-email-unsubscribe/index.ts:4
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/handle-email-unsubscribe/index.ts:4 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/preview-transactional-email/index.ts:6
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/preview-transactional-email/index.ts:6 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/send-transactional-email/index.ts:21
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
supabase/functions/send-transactional-email/index.ts:21 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/components/ui/chart.tsx:70
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/components/ui/chart.tsx:70 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in src/pages/BlogPost.tsx:191
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
src/pages/BlogPost.tsx:191 Dangerous innerhtml
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 52 placeholder/mock markers across 21 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
5 test file(s) for 216 source file(s) (ratio 0.02). 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 10 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 Docs conf 1.00 README lacks setup or run instructions
A README exists, but it does not contain common install/setup/run markers. This matches a frequent generated-code pattern: UI is present, operational handoff is thin.
ReadmeRepo 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/prerender.ts:178
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 — supabase/functions/auth-email-hook/index.ts:214
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 — supabase/functions/handle-email-suppression/index.ts:127
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 — supabase/functions/handle-email-unsubscribe/index.ts:127
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 — supabase/functions/payments-webhook/index.ts:76
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 — supabase/functions/send-transactional-email/index.ts:198
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 quality Complexity conf 1.00 Very large file: src/pages/Index.tsx (1003 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/17ea24f9-7ab1-4f2e-9ee4-aad43c86d325/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/17ea24f9-7ab1-4f2e-9ee4-aad43c86d325/

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.