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.

cabjo2026-glitch/rideapp-driver

https://github.com/cabjo2026-glitch/rideapp-driver · scanned 2026-06-17 01:45 UTC (1 month, 1 week ago)

34 raw signals (0 security + 34 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 34 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

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 73.1/100 with 88.9% coverage. It contains 489 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 34 findings — concentrated in quality (19), frontend (8), security (5). Risk profile is high: 2 critical, 0 high, 10 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 23 of 34 actionable findings. 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 security conf 1.00 Insecure pattern 'private_key_in_repo' in supabase/functions/send-notification/index.ts:46

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

supabase/functions/send-notification/index.ts:46 Private key in repo

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — playwright.config.ts:19

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/_shared/zain_sms_service.ts:39

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/dispatch-ride/index.ts:373

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/send-notification/index.ts:70

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 ci, lockfile. 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 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 'cors_wildcard' in supabase/functions/admin-finance/index.ts:35

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

supabase/functions/admin-finance/index.ts:35 Cors wildcard

medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/request-otp/index.ts:59

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

supabase/functions/request-otp/index.ts:59 Cors wildcard

medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in supabase/functions/verify-otp/index.ts:41

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

supabase/functions/verify-otp/index.ts:41 Cors wildcard

medium System graph quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration

A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.

Runtime configService clientGenerated repo pattern

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

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

Repo hardeningGenerated repo pattern

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

Found 110 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 dependencies conf 1.00 Node manifest has dependencies but no lockfile: scripts/package.json

`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.

scripts/package.json LockfileReproducibilityGenerated repo pattern

low System graph software Dead code conf 1.00 Possibly dead Python function: info

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

scripts/audit_production.py:33

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/e2e-test-cleanup.js:25