Schema and UI assumptions do not match.
VibeFix
Check Lovable plus Supabase apps for launch-risk gaps
VibeFix reviews generated Lovable flows against Supabase auth, RLS, schema, admin, and deployment requirements.
main · 84 files mapped · spec coverage compared · no source stored
Launch Readiness62/100
Security RiskHigh
Missing Features7
Production Blockers5
Highest leverage finding
Payment state can drift from app state
Checkout can succeed while booking and entitlement records remain incomplete after webhook retries.
$4,500 to $7,500
app/api/stripe/webhook/route.tssupabase/policies.sqltests/checkout.spec.tsNext: make webhook persistence idempotent, add paid-state recovery, then re-scan.
Lovable plus Supabase blockers
VibeFix separates symptoms from launch blockers.
Preview auth differs from production behavior.
RLS policies do not cover generated flows.
What you get
A report that explains the risk and the next patch boundary.
Each finding has a plain-English founder summary and expandable technical evidence with affected files, recommended fixes, acceptance criteria, and regression cautions.
Schema-to-UI map
RLS review
Admin checks
Fix vs rebuild guidance
Sample findings
The output is specific enough to scope repair work.
The UI assumes an approval status field that is not enforced in policy.
Admin edits bypass the intended role model.
Trust FAQ
Clear access boundaries before code is uploaded.
Do you support private repos?
Yes. The intended production integration uses read-only GitHub access for private repositories. ZIP exports are also supported for Lovable, Bolt, Replit, and similar tools.
Do you train models on my code?
No. The product promise is analysis only. Customer code is not used for model training, and deeper review runs through RubberDuck semantic analysis.
Can I delete my project?
Yes. V1 is designed around delete-after-report controls and revocable repo access. Production storage should enforce deletion and retention policies.
What access do you need?
VibeFix needs read-only source access or a ZIP export, plus any spec, PRD, screenshots, or notes that describe what the app should do.
Launch-readiness report
Turn the app into a launch plan
Upload the repo and spec. Get the gaps, risks, prompt pack, and repair quote before the next sprint decision.