<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Ida Zhang</title>
    <description>The latest articles on DEV Community by Ida Zhang (@ida_zhang_cc496f24f8c03ef).</description>
    <link>https://dev.to/ida_zhang_cc496f24f8c03ef</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4052299%2F205e94ef-f116-4fcb-afdc-6cd56bac267f.png</url>
      <title>DEV Community: Ida Zhang</title>
      <link>https://dev.to/ida_zhang_cc496f24f8c03ef</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ida_zhang_cc496f24f8c03ef"/>
    <language>en</language>
    <item>
      <title>I Scanned 75 AI-Generated Code Files Every Night. 81% Had at Least One Issue.</title>
      <dc:creator>Ida Zhang</dc:creator>
      <pubDate>Wed, 29 Jul 2026 09:09:37 +0000</pubDate>
      <link>https://dev.to/ida_zhang_cc496f24f8c03ef/i-scanned-75-ai-generated-code-files-every-night-81-had-at-least-one-issue-43co</link>
      <guid>https://dev.to/ida_zhang_cc496f24f8c03ef/i-scanned-75-ai-generated-code-files-every-night-81-had-at-least-one-issue-43co</guid>
      <description>&lt;p&gt;A few weeks ago I started a small experiment: every night, I ran automated scans over AI-generated code files — code written by Copilot, Cursor, ChatGPT and friends, collected from real projects.&lt;/p&gt;

&lt;p&gt;The results after scanning &lt;strong&gt;75 files&lt;/strong&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;81%&lt;/strong&gt; contained at least one issue&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;2,277&lt;/strong&gt; findings in total&lt;/li&gt;
&lt;li&gt;That's an average of &lt;strong&gt;30 issues per file&lt;/strong&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Not style nitpicks. Real, shippable bugs.&lt;/p&gt;

&lt;h3&gt;
  
  
  The most common offenders
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;1. Hallucinated APIs.&lt;/strong&gt; The AI confidently calls a function that doesn't exist — in the library version you actually have installed. It compiles in your head, it doesn't compile in CI.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Placeholder URLs.&lt;/strong&gt; &lt;code&gt;https://api.example.com/...&lt;/code&gt; left in "finished" code. It looks intentional. It ships. It 404s in production at 2am.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. SQL built with string formatting.&lt;/strong&gt; &lt;code&gt;f"SELECT * FROM users WHERE id = {uid}"&lt;/code&gt; — the AI knows this is wrong. It writes it anyway, because it's the pattern that most often "works" in training data.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Silent fallbacks.&lt;/strong&gt; A &lt;code&gt;try/except&lt;/code&gt; that swallows every error and returns a default. Your code never crashes. It also never tells you it's broken.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5. Hardcoded secrets.&lt;/strong&gt; API keys and tokens pasted straight into source. The AI saw it a thousand times in tutorials, so it reproduces it.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why AI keeps making these mistakes
&lt;/h3&gt;

&lt;p&gt;AI code assistants optimize for &lt;em&gt;plausible&lt;/em&gt; code, not &lt;em&gt;correct&lt;/em&gt; code. They reproduce the statistical center of GitHub — including its bugs, its outdated APIs, and its bad habits from 2019 tutorials.&lt;/p&gt;

&lt;p&gt;The better the AI gets at writing code that &lt;em&gt;looks&lt;/em&gt; right, the worse our review habits get. When 200 lines appear in 10 seconds, nobody reads line 137.&lt;/p&gt;

&lt;h3&gt;
  
  
  So I built a thing
&lt;/h3&gt;

&lt;p&gt;I got tired of finding these by hand, so I turned the nightly scanner into a VS Code extension: &lt;strong&gt;CodeVouch&lt;/strong&gt;. It scans the AI-generated code in your workspace for exactly these patterns — hallucinated APIs, placeholder URLs, SQL string formatting, silent fallbacks, hardcoded secrets — and shows a quality report before you ship.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Marketplace: &lt;a href="https://marketplace.visualstudio.com/items?itemName=codevouch-ai.codevouch" rel="noopener noreferrer"&gt;https://marketplace.visualstudio.com/items?itemName=codevouch-ai.codevouch&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Website: &lt;a href="https://codevouch.codes" rel="noopener noreferrer"&gt;https://codevouch.codes&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;GitHub (open detection rules — star us!): &lt;a href="https://github.com/8rabbits/CodeVouch" rel="noopener noreferrer"&gt;https://github.com/8rabbits/CodeVouch&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It's free for scanning; a Pro tier adds deep review. But honestly, the point of this post isn't the tool — it's the data.&lt;/p&gt;

&lt;h3&gt;
  
  
  The takeaway
&lt;/h3&gt;

&lt;p&gt;If you ship AI-generated code without reviewing it, you're shipping bugs at AI speed. Review it — with your eyes, with a scanner, with anything. Just don't skip it.&lt;/p&gt;

&lt;p&gt;I'm continuing the nightly scans. If people are interested, I'll publish a full breakdown of the 2,277 findings — which AI models produce which bugs, and which categories are getting worse.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>codequality</category>
      <category>vscode</category>
    </item>
  </channel>
</rss>
