Auth and permissions
Protected routes, admin screens, user data separation, session expiry, password reset, and redirect loops.
Lovable, Bolt, Replit, Cursor, v0, Base44
I triage AI-built apps when the preview looks fine but real users, real payments, real auth, or real deployment starts breaking.
What gets checked
Protected routes, admin screens, user data separation, session expiry, password reset, and redirect loops.
Public keys, private keys, browser-only leaks, environment variables, test/live credentials, and API route boundaries.
Stripe modes, webhook verification, duplicate fulfillment, retry handling, failed checkout states, and subscription access.
Supabase/Firebase access rules, table ownership, unauthenticated reads, cross-user reads, and destructive mutations.
Build scripts, missing variables, server/client mismatch, broken preview-to-production assumptions, and log-based debugging.
Large generated files, repeated logic, dead mock data, weak error states, and the smallest refactor needed before growth.
Free repo scanner
Looks for private-looking keys, public frontend env vars that should not be public, and Supabase service-role references.
Flags Stripe webhook handlers without visible signature checks, missing Firebase rules, and Supabase projects without RLS evidence.
Checks for debug API routes, missing AI usage guardrails, weak release hygiene, and handoff gaps that slow down cleanup.
npx --yes shipcheck-cli .
Open the Shipcheck tool page for npm, GitHub, report export, and paid review options.
Pricing
Repo/live-app triage, risk notes, reproduction steps where possible, and a ranked fix plan. Best when you are unsure what is broken.
Pay after scope confirmationOne focused repair path: deploy failure, auth issue, payment bug, database rule cleanup, or a critical user flow that must ship.
Open deposit linkBroader cleanup for apps with users: security pass, error handling, key flows, test checklist, deploy notes, and maintainability fixes.
Boundary
You can send a repo, invite me to a project, paste logs, or share a public link you control.
I can review configuration, code, rules, deploy logs, headers, and normal user flows for launch risk.
No credential guessing, data scraping, invasive scanning, or probing systems without clear permission.
Start with the blocker