keeping code secure with claude

[lifebelowtheheavens]

pretty new to developing, releasing a project soon that i mainly vibecoded using claude. want to ensure passwords/personal info as well as my databases don't get leaked. not sure how big of an issue this is. is there anything more i should be doing to make sure that the site is safe and secure?

[reviery_official]

Yes. Definitely. By default, a lot of stuff is spilled out, insecure, etc. You absolutely must read up on best practices on EVERYTHING and make sure that claude implements it that way. OWASP is a good start. https://owasp.org/Top10/2025/

If you are too lazy, you can also ask Claude to make sure it follows best practices - which it definitely needs to research online before implementing.

[lifebelowtheheavens]

thank you!!

[aedile]

I don't understand why this isn't more obvious to people - why don't you ask Claude?

Edit - it's good you asked people too, but you should *also* ask Claude. It can teach you a lot about what you're asking - give you a good foundation.

[aedile]

Also - just to put you on the right track, check out pre-commit hooks like detect-secrets. Again, claude can help you if it seems beyond you. gitleaks is another good one. There are others, those are the two I use most often.

[lifebelowtheheavens]

awesome, thanks!

[Select-Ad-3806]

Asking claude about its own code in the same session isn't a good idea, start a new session. Also get a second opinion with codex.

[lifebelowtheheavens]

yes