Vibe-coding is fun until your Supabase table leaks customer data.
Common AI-built app issues we keep seeing:
-RLS disabled
-exposed API keys
-open Firebase rules
-users accessing other users’ data
-admin access protected only in the UI
“Built with AI” is not a legal defense.
@Aakashroy32@mscode07 Following up here since our previous messages may have been missed we’re still seeing what appears to be a publicly accessible data exposure affecting your application.
We’re intentionally not sharing details publicly, but it would be worth reviewing as soon as possible.
@Udit060@anupamrjp Following up here since our previous messages may have been missed — we’re still seeing what appears to be a publicly accessible data exposure affecting your application.
We’re intentionally not sharing details publicly, but it would be worth reviewing as soon as possible.
@Aakashroy32 Quick heads up, we ran it through a security check and it flagged a potential database exposure that might be worth reviewing before wider use.
Happy to share details privately if helpful.
@imgabrielonx@victor_bigfield This looks awesome ,quick heads up, we ran it through a security check and it flagged a potential database exposure that might be worth reviewing before wider use.
Happy to share details privately if helpful.
@trevorlasn@Peter_Soida Hey @trevorlasn our security scanner flagged a few issues on your API worth looking at. Nothing posted publicly. DM us or reach out at [email protected] and we'll share the full report.
Today we’re excited to announce that @AvariAi_1 is partnering with @polydefender , a fast-growing security startup from Spain helping developers find exposed keys, auth gaps, and risky dependencies before shipping their platform , This partnership aligns with our mission .
@kaushikp010@heyblake Sounds good , when you are ready just DM and we will whitelist the platform for the closed beta and get a PRO membership for free .
Good luck!
@JavierForge@danielkempe There are a few patterns here that can lead to problems in production setups.
Probably worth validating early. We’re currently helping a few teams catch these in beta if you’d like us to check.
@BobTheAICEO@KaiXCreator There are a few patterns here that can lead to problems in production setups.
Probably worth validating early. We’re currently helping a few teams catch these in beta if you’d like us to check.
@anoop_sasi92@MicroLaunchHQ Noticed a couple of things that could introduce issues depending on how this is configured.
Might be worth a quick pass before wider release. We’re reviewing projects like this in a small beta group if useful.
@kaushikp010@heyblake Some parts of this setup might behave differently under real usage conditions.
Worth reviewing before scaling it out. Happy to include it in our beta reviews if helpful.
@dennisadzisam@ardent__dev Flagged a couple of things worth checking before wider use.
Let me know if you want a deeper review we’re running a small beta.
@RedScore_AI@heyblake There are a few patterns here that can lead to problems in production setups.
Probably worth validating early. We’re currently helping a few teams catch these in beta if you’d like us to check.
@islamtaha@MicroLaunchHQ Noticed a couple of things that could introduce issues depending on how this is configured.
Might be worth a quick pass before wider release. We’re reviewing projects like this in a small beta group if useful.