<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: aakashpawar</title><link>https://news.ycombinator.com/user?id=aakashpawar</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 22 Oct 2026 04:59:33 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=aakashpawar" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by aakashpawar in "Compromised LiteLLM 1.107.0 on PyPI Installs a Credential Stealer and Backdoor"]]></title><description><![CDATA[
<p>If that's right then attestations wouldn't have saved anyone here either. They prove which workflow published the wheel, not what source that workflow checked out. A private pipeline building from the same-looking repo still gives you a perfectly valid attestation.<p>What would catch it is someone rebuilding from the public tag and comparing the result, which almost nobody does for the python wheels. I have been treating attestations as the answer for my own project's releases, so this is a good reminder of where they stop.</p>
]]></description><pubDate>Wed, 21 Oct 2026 16:45:38 +0000</pubDate><link>https://news.ycombinator.com/item?id=50183906</link><dc:creator>aakashpawar</dc:creator><comments>https://news.ycombinator.com/item?id=50183906</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=50183906</guid></item></channel></rss>