this post was submitted on 12 Sep 2026
124 points (100.0% liked)
Programming
28481 readers
152 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Boy it's amazing how people ignore the security track record of human authored code over the last 30 years. One need only look at the recent explosion of discovered vulnerabilities by AI.
This license is fud.
Nobody is ignoring anything.
It’s not a license, it’s a policy.
AI tends to “discover” previously discovered vulnerabilities, or obvious vulnerabilities. It also tends to hallucinate vulnerabilities. I’m not saying it’s useless at discovering vulnerabilities, just that a human audit is better.
The policy also doesn’t say you can’t use AI to audit a code base, or even a single diff, so that point is moot.
Friend - your information is very out-of-date. It's accelerating the discovery of vulnerabilities like crazy. I'm not saying we've hit singularity (or even that we will) but to brush it all off as "it only finds things we already knew about" is copium at this point.
Well it’s a good thing I didn’t say that then. xD
I think you’re also missing the bigger point that the policy does not prevent you from auditing your code base with AI. That is completely, 100% allowed under this policy.
Reading comprehension is important.