<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security Vulnerabilities in AI-Generated Code: A Large-Scale Analysis of Public GitHub Repositories · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2510.26103/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:27:26 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2510.26103/feed.xml" rel="self" type="application/rss+xml" /><item><title>Security Vulnerabilities in AI-Generated Code: A Large-Scale Analysis of Public GitHub Repositories — HN submission</title><link>https://news.ycombinator.com/item?id=46820686</link><guid isPermaLink="false">urn:hackerpapers:submission:2510.26103:46820686</guid><pubDate>Fri, 30 Jan 2026 04:58:43 GMT</pubDate><description>&lt;p&gt;Show HN: I made a dev tool that helps vibecoders to AVOID security issues&lt;/p&gt;&lt;p&gt;The first time I have heard about the vibecoding I could not believe that peeps without the technical background dare to release web apps and other type of software within the week of using such stuff like cursor, claude code and later lovable, bolt.new and etc. I saw some of the projects like that and despite them being somewhat functional - I could feel that security was not the strongest side of these pieces of software. As it turned out I was not hallucinating about the existance of the said security problem - lots of papers were published in this regard. For example, just last quarter 2…&lt;/p&gt;&lt;p&gt;1 point; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2510.26103/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item></channel></rss>
