I built a free scanner for Lovable, Replit and Bolt apps.
Paste your live URL, get an A–F grade in 30 seconds:
- security headers
- open CORS
- dev banner left in prod
- robots, sitemap, SEO basics
Read-only. Fix prompts you paste into your builder.
https://t.co/Nl2g6Yt0JY
Question à la communauté 👇
Vous connaissez une solution 100 % gratuite et open source pour vérifier une grosse base de données d’adresses e-mail (100k à 200k contacts) ?
L’objectif :
Détecter les adresses inexistantes ou désactivées.
Vérifier les domaines et les serveurs MX.
Identifier les adresses invalides ou à risque.
Éviter les hard bounces avant une campagne Brevo.
Je cherche une solution sans API payante, sans abonnement et idéalement hébergeable en Europe.
Scripts Python, GitHub ou projets open source bienvenus !
Vous utilisez quoi ?
@matthewvenn What I'd ask them:
1. What do you make students do by hand before they're allowed to use AI?
2. How do you check AI output you can't fully verify yourself?
3. Which design decisions should never be delegated?
4. Has AI changed what it means to "know" analog design?
Most of these follow the same recipe:
1. Song first: write the parody lyrics, generate it in Suno
2. One clean still per character (Seedream or GPT Image)
3. Animate in chunks of 15s or less with Seedance 2.x or MiniMax H3 on fal, with the song chunk as the audio reference for lip sync
4. Re-lipsync the shots where the mouth looks off, then cut on the beat
About $5 for a 20s clip, closer to $100 for a polished minute.
Happy to. For the YC submit, 3 quick fixes: 1) in your Replit server, serve static files (sitemap.xml with an XML content-type) BEFORE the SPA catch-all, so it stops returning index.html. 2) make the catch-all return a real 404 status for unknown routes (keep a list of valid routes), so crawlers don't see every URL as a 200. 3) 301 the bio-link domain to your main site. Takes ~20 min. I can walk through it with you free if useful; my DMs are locked, so reply here.
Works in preview, dead in prod. Server listened on localhost:3000. Fix: listen on 0.0.0.0 and process.env.PORT, copy every workspace secret into the deployment secrets, redeploy.
Which one have you hit?
Every bug I find in vibe-coded apps (Replit, Lovable, Bolt), in one thread. Real cases from audits and fixes, no app names. One post per bug: what broke, why, the exact fix. Bookmark it, I add new ones as I find them 🧵
Webhooks with no replay guard. Stripe retries events, so a handler without a check can create the same order twice. Fix: store https://t.co/UXENGmw0v0, skip if already processed. Test: send the same event twice, the second must change nothing.
@Lucid_Dlirium@amasad@OpenAI Congrats on applying! Before you submit Monday, Nov 2: the link in your bio serves the app shell on every URL, so dead links return 200 and /sitemap.xml comes back as HTML. A 301 to your main site fixes both. Happy to do a free 15-min check of your demo. — Simo
Supabase flips a default tomorrow (Oct 30).
New tables in public stop being reachable from supabase-js until you GRANT them. Your next Lovable/Bolt feature will just fail with "42501 permission denied".
Existing tables don't change.
Fix per new table:
grant select, insert, update, delete on public.t to authenticated;
Never GRANT ALL.
Built on Lovable + Supabase? Reply "grants" and I'll check yours free.
Taking 3 vibe-coded apps this weekend.
Built with Replit, Lovable, Bolt or Cursor? Before real users hit it, I check exposed keys, open database rules, login and payments, then fix what's broken.
$49 for the first 3 founders (normally $149). You pay once the fix works.
What's the one thing you're scared will break at launch?
Feature request: make usage visible before I hit the wall.
I hit the limit way faster than expected and have no idea which requests burned it. Please add:
• a live usage meter + cost per reply (long context and tool calls feel 10x heavier)
• a warning at 80% instead of a hard stop
• an option to auto-switch to a lighter model instead of blocking me
I'd happily spend my quota smarter if I could see it.
I'm in 🙋♂️
Solving: founders shipping apps built with Replit, Lovable, Bolt or Cursor that leak data or break in prod (open APIs, public DB tables, exposed keys). Safe to Launch: I find the issues, fix them, verify, in 48h. $149, 14-day guarantee.
In 2 months: 20 paying founders and $1.5k/month with Care retainers.
https://t.co/AzDFMuPO65
Replit just asked users to republish their apps.
Node.js shipped high-severity fixes on Oct 21, and eMudhra's certificate keys were compromised.
On Python or a Reserved VM? You're not patched until you hit Publish again. Same URL, 30 seconds.
Do it today.
Claude Security now re-scans your repo on every change. Big deal, if you're on Claude Enterprise.
Built your app solo on Lovable, Replit or Bolt? No Enterprise, no repo hooked up.
AI finds the issues. I verify each by hand, fix it and ship it.
Free audit in 24h: https://t.co/AzDFMuPO65
Claude Security now keeps up with your code as it changes.
Connect your repositories once. Claude runs a deep first scan, then re-scans as changes land, so findings stay close to the current state of your code.
In public beta on Claude Enterprise.
The friction is usually per-tool API keys and context handoff, not the model itself. Look for an orchestrator that routes by task and shares one conversation context, and verify the billing comes from your own provider key rather than the tool's managed key so switching models doesn't surprise you.
@develoveloper@Lovable Ask support to put the exact rule they applied in writing (paid amount above $0 vs any converted paid signup). The referral terms are what they'll go by, and a screenshot of your referral dashboard status helps the case.