<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: Acacian</title><link>https://news.ycombinator.com/user?id=Acacian</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 15 Jun 2026 02:42:28 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=Acacian" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by Acacian in "Show HN: I tested 11 AI frameworks for basic security – none passed"]]></title><description><![CDATA[
<p>LangChain, CrewAI, OpenAI Agents, Anthropic, LiteLLM, Pydantic AI,                                                       
Google ADK — I went through 11 frameworks looking for basic runtime                                                      
security: injection detection, PII masking, audit trails. None of                                                        
them had it.<p>So I built a monkey-patching layer that intercepts LLM calls and
runs them through guardrails:<p>import aegis; aegis.init()<p>Patches whatever frameworks you have installed. ~2.6ms overhead.<p>The nastiest find: streaming responses skip middleware entirely.                                                         
Content leaks before any check runs. I wrote a streaming engine
that auto-selects between windowed scanning and full buffering                                                           
depending on what the guardrail needs — PII like "078-05-1120"                                                         
can split across chunks, so regex won't catch it without the
full buffer.<p>Context: <a href="https://github.com/langchain-ai/langchain/issues/35011" rel="nofollow">https://github.com/langchain-ai/langchain/issues/35011</a>                                                          
Source: <a href="https://github.com/Acacian/aegis" rel="nofollow">https://github.com/Acacian/aegis</a></p>
]]></description><pubDate>Thu, 02 Apr 2026 15:53:18 +0000</pubDate><link>https://news.ycombinator.com/item?id=47616145</link><dc:creator>Acacian</dc:creator><comments>https://news.ycombinator.com/item?id=47616145</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47616145</guid></item><item><title><![CDATA[Show HN: I tested 11 AI frameworks for basic security – none passed]]></title><description><![CDATA[
<p>Article URL: <a href="https://acacian.github.io/aegis/playground/">https://acacian.github.io/aegis/playground/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47616116">https://news.ycombinator.com/item?id=47616116</a></p>
<p>Points: 1</p>
<p># Comments: 1</p>
]]></description><pubDate>Thu, 02 Apr 2026 15:51:53 +0000</pubDate><link>https://acacian.github.io/aegis/playground/</link><dc:creator>Acacian</dc:creator><comments>https://news.ycombinator.com/item?id=47616116</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47616116</guid></item><item><title><![CDATA[Show HN: Aegis – Security framework for AI agents]]></title><description><![CDATA[
<p>Article URL: <a href="https://acacian.github.io/aegis/playground/">https://acacian.github.io/aegis/playground/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47542749">https://news.ycombinator.com/item?id=47542749</a></p>
<p>Points: 3</p>
<p># Comments: 0</p>
]]></description><pubDate>Fri, 27 Mar 2026 14:00:05 +0000</pubDate><link>https://acacian.github.io/aegis/playground/</link><dc:creator>Acacian</dc:creator><comments>https://news.ycombinator.com/item?id=47542749</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47542749</guid></item><item><title><![CDATA[New comment by Acacian in "90% of Claude-linked output going to GitHub repos w <2 stars"]]></title><description><![CDATA[
<p>The base rate argument here is the right one. I maintain a solo project with 3,800+ tests and 92% coverage — zero stars for months because I never promoted it. Stars measure marketing, not quality.<p>What's more interesting to me is that Claude dramatically lowers the barrier to _testing_, not just writing code. I can mass-generate edge case tests that I'd never bother writing manually. The result is higher-quality solo repos that look "abandoned" by star count.<p>Is anyone tracking test coverage or CI pass rates for AI-assisted repos vs traditional ones? That seems like a much more useful signal than stars.</p>
]]></description><pubDate>Thu, 26 Mar 2026 12:21:49 +0000</pubDate><link>https://news.ycombinator.com/item?id=47529586</link><dc:creator>Acacian</dc:creator><comments>https://news.ycombinator.com/item?id=47529586</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47529586</guid></item><item><title><![CDATA[New comment by Acacian in "Ask HN: Is using AI tooling for a PhD literature review dishonest?"]]></title><description><![CDATA[
<p>The verification pipeline is the most valuable part of your workflow. Most people who use AI for literature reviews skip exactly that step — they trust the output and move on.<p>What you're describing is closer to building a testing harness than "using AI to write." You're asserting claims, checking them against source PDFs, and reviewing manually. That's more rigorous than most manual lit reviews where people skim abstracts and cite papers they half-read.<p>Document the pipeline as methodology in your dissertation. That turns a potential misconduct question into a contribution.</p>
]]></description><pubDate>Tue, 24 Mar 2026 12:52:12 +0000</pubDate><link>https://news.ycombinator.com/item?id=47501877</link><dc:creator>Acacian</dc:creator><comments>https://news.ycombinator.com/item?id=47501877</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47501877</guid></item></channel></rss>