> We immediately disclosed the issue to the Moltbook team, who secured it within hours with our assistance
How do you go about telling a person who vibe-coded a project into existence how to fix their security flaws?
> We immediately disclosed the issue to the Moltbook team, who secured it within hours with our assistance
How do you go about telling a person who vibe-coded a project into existence how to fix their security flaws?
Claude generated the statements to run against Supabase and the person getting the statements from Claude sent it to the person who vibe-coded Moltbook.
I wish I was kidding but not really - they posted about it on X.
Claude is very good at writing SQL. You still need to review and understand it.
I recently started a new Supabase project and used Claude to write all migrations related to RLS and RBAC.