critical System graph security Secrets conf 1.00 2 occurrences Possible secret in src/routes/rev-ops-7k2p.tsx

Detected pattern matching password_literal. Rotate the credential and move to a secret manager.

lines 1011, 1401

src/routes/rev-ops-7k2p.tsx:1011, 1401 (2 hits)

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — convex/googleCalendar.ts:98

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/components/analytics/MapTab.tsx:52

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 'local_storage_auth_token' in src/lib/user-store.ts:85

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

src/lib/user-store.ts:85 Local storage auth token

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

Found 93 placeholder/mock markers across 25 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 191 source file(s) (ratio 0.01). Consider adding integration or unit tests for critical paths.

Coverage

low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — src/components/AdminBookingCalendar.tsx:364

A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…

Fq active light bg

low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — src/components/BookingCalendar.tsx:441

A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…

Fq active light bg

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

Found 31 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 frontend Frontend quality conf 1.00 Icon-only button without accessible name — src/components/AdminBookingDetailsModal.tsx:229