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.

walczaq/guideapp

https://github.com/walczaq/guideapp · scanned 2026-06-16 00:54 UTC (2 months, 1 week ago)

24 raw signals (0 security + 24 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 24 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 · 24 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 13 Low 3 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 24 Crowd 0 Layer: Frontend 1 Security 8 Quality 15

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 76.3/100 with 66.7% coverage. It contains 161 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 24 findings — concentrated in quality (15), security (8), frontend (1). Risk profile is low: 0 critical, 0 high, 13 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 16 of 24 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 quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — supabase/functions/translate_stop_notes/index.ts:42

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/translate_tour/index.ts:34

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 Tests conf 1.00 CI is configured but no tests are detected

A CI pipeline exists, but the scan found no test files to gate. Opus labeled this generated-code pattern as config theater: release machinery exists, but it has little behavioral signal.

CI/CDConfig theaterRepo hardening

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

Multiple low-cost hardening controls are missing together: license, tests, 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 security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/guide_media_upload/index.ts:17

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

supabase/functions/guide_media_upload/index.ts:17 Cors wildcard

medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/translate_stop_notes/index.ts:32

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

supabase/functions/translate_stop_notes/index.ts:32 Cors wildcard

medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/translate_tour/index.ts:24

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

supabase/functions/translate_tour/index.ts:24 Cors wildcard

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in v0.1.html:580