RLS is disabled or incomplete for key tables.
CodeFix
Audit Supabase auth, RLS, and data access before launch
CodeFix checks whether user-owned data, admin paths, and sensitive tables are protected by real server-side and RLS evidence.
Highest leverage finding
Payment state can drift from app state
Checkout can succeed while booking and entitlement records remain incomplete after webhook retries.
app/api/stripe/webhook/route.tssupabase/policies.sqltests/checkout.spec.tsSupabase checks
CodeFix separates symptoms from launch blockers.
Queries trust client-side user IDs.
Admin paths do not verify roles server-side.
What you get
A report that explains the risk and the next safe patch boundary.
Each finding has a plain-English founder summary plus technical evidence with affected files, recommended fixes, acceptance criteria, and regression cautions.
Sample findings
The output is specific enough to scope repair work.
Tutor records can be listed without organization scoping.
An update path relies on UI visibility instead of a policy.
Trust FAQ
Clear access boundaries before code is uploaded.
Do you support private repos?
Yes. CodeFix supports private GitHub repositories and ZIP exports. Repository access is used only to inspect the code needed for launch-readiness analysis.
Do you train models on my code?
No. Customer code is analyzed for the report and is not used for model training. Deeper proof runs through configured live analysis.
Can I delete my project?
Yes. Projects are built around delete-after-report controls and revocable access so uploaded code does not need to remain in the system longer than necessary.
What access do you need?
CodeFix needs source access or a ZIP export, plus any spec, PRD, screenshots, or notes that explain what the app should do and what is currently failing.
Launch-readiness report
Get the proof-to-ship plan before the next rebuild debate
Upload the repo and spec. Get the gaps, risks, repair scope, and repair-budget estimate before the next sprint decision.