<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Anomalicious: Automated Detection of Anomalous and Potentially Malicious Commits on GitHub · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2103.03846/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2103.03846/feed.xml" rel="self" type="application/rss+xml" /><item><title>Anomalicious: Automated Detection of Anomalous and Potentially Malicious Commits on GitHub — mentioned by kekebo</title><link>https://news.ycombinator.com/item?id=30790798</link><guid isPermaLink="false">urn:hackerpapers:mention:2103.03846:30790798</guid><pubDate>Thu, 24 Mar 2022 14:58:45 GMT</pubDate><description>&lt;p&gt;Could (/should) this be mitigated on the repository host side by scanning for and flagging malicious commits? A paper from last year evaluating this on Github achieves a ~50% success rate[0]. Given Github already training ml models across all repositories for Copilot I would guess higher rates would be possible. [0] https://arxiv.org/abs/2103.03846 Edit: add link&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2103.03846/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.SE</category></item></channel></rss>
