<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code Security on No Semicolons</title><link>https://nosemicolons.com/tags/code-security/</link><description>Recent content in Code Security on No Semicolons</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 18 May 2026 11:38:44 +0000</lastBuildDate><atom:link href="https://nosemicolons.com/tags/code-security/index.xml" rel="self" type="application/rss+xml"/><item><title>The AI Code Generation Time Bomb: How Outdated Models Are Sabotaging Your Codebase</title><link>https://nosemicolons.com/posts/ai-code-generation-time-bomb-outdated-models/</link><pubDate>Mon, 18 May 2026 11:38:44 +0000</pubDate><guid>https://nosemicolons.com/posts/ai-code-generation-time-bomb-outdated-models/</guid><description>&lt;p>Ever noticed your AI coding assistant suggesting patterns that make you go &amp;ldquo;hmm, that feels&amp;hellip; old&amp;rdquo;? You&amp;rsquo;re not imagining things. There&amp;rsquo;s a growing problem in AI-assisted development that we need to talk about: the models we rely on are often trained on codebases from years past, and they&amp;rsquo;re quietly introducing outdated practices, deprecated APIs, and even security vulnerabilities into our shiny new projects.&lt;/p>
&lt;p>I learned this the hard way when Claude suggested using &lt;code>request&lt;/code> for a Node.js HTTP client in a recent project. Sure, it worked, but &lt;code>request&lt;/code> has been deprecated since 2020. It got me thinking about how many other time bombs might be lurking in AI-generated code.&lt;/p></description></item></channel></rss>