@uday_devops · X

@Sakthi_in · X

- Ship AI written code confidently. Catch drift before it compounds.

@emir_ogz · X

Just shipped - AI-native workspace for solo devs Agent reads/writes your project notes automaticly

@SolaDugbo · X

You should join our vibe coding leaderboard. it's all open source

@unemployeeonarc · X

42069 seconds of vibe coding later Unemployee Smack is finally here ~ meme gallery updated

@djdeepakjha · X

AI can build your startup in days. But who checks the security? Public configs. Weak APIs. Exposed secrets. If AI built your app, scan it before someone else does. 🔒 StackSecured — security assessment #CyberSecurity #VibeCoding #AppSecurity

@mesba969 · X

paste an Amazon ASIN, it reads the product's reviews and hands back a fix plan: exact listing copy, supplier notes, FAQ answers. Most review tools stop at 'here's the sentiment' — this ships the actual edits.

@atenyun · X

Hi everyone! If you're getting into vibe coding and have questions about LSPs or need a hand with reviewing your smart contract, feel free to post on Hup. We're here to help you out! Creator: 0x20e229667Cec8A0e9D3C6Fb89693B2a44ec2C50e via @hupsocial

@codewithnovel · X

glad to know how much relevant my SaaS currently !

u/Still_Amphibian545 · Reddit

almost launched a side project with my api keys sitting in the repo (a week free gpt 5.6 on us) was about a day from launching a small project when i noticed my openai key was just sitting in a committed file. it had been there for weeks. no idea how i missed it. made me wonder what else was wrong that i couldn't see. turns out for vibecoded stuff it's usually the same handful of things. secrets in the repo, endpoints with no auth, a database with no access rules, no limit on the ex

@MrBallaz · X

Protect your vibe-coded app

@ace_space_1 · X