Back

Havish

. • 2m

The issue is that most people just get the ai gen code, replace the API keys and deploy it. That's what causes these issues. Also api key being exposed is small thing, no one (including me 🤐) cares about security while vibe coding. “env var in production” 😂😂😭

Reply

More like this

Recommendations from Medial

Image Description
Image Description

Chamarti Sreekar

Passionate about Pos... • 2m

Somebody just scanned 2000 Vibecoded websites... and here's what he found : - 49.5% had security issues - Found 1120 JWT tokens exposed - 70 Google API keys floating around And yes, env vars in production 🤦‍♂️ Security ain't a vibe if you're lea

See More
4 Replies
1
19

Somen Das

Senior developer | b... • 1m

I messed up things. I am building an opensource package to connect multiple S3 compatible services like cloudflare r2, digitalocean etc. so when testing I used original API keys and I totally forgot to remove things and just did npm publish. and the

See More
Reply
3

Subhajit Chatterjee

From India For World • 1d

Forget switching to a new AI browser. Anneshon.ai is a powerful Chrome extension that brings intelligent automation directly to your current browser. Instantly summarize web pages, translate text, and let our AI draft and schedule emails for you. It

See More
Reply
2

Gigaversity

Gigaversity.in • 2m

One missing .env file nearly took our production down. During one of our projects, a routine deployment went live with everything seemingly in order. But moments later, critical services started failing, and our team quickly realized that something

See More
Reply
14

Download the medial app to read full posts, comements and news.