<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: jostkolega</title><link>https://news.ycombinator.com/user?id=jostkolega</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 23 Apr 2026 07:28:29 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=jostkolega" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by jostkolega in "Ask HN: What are you working on? (February 2026)"]]></title><description><![CDATA[
<p>Nice! Working in a similar space -  will be publishing here also soon. How are you handling finding issues beyond pattern matching where deep code understanding is required?</p>
]]></description><pubDate>Tue, 10 Feb 2026 18:36:53 +0000</pubDate><link>https://news.ycombinator.com/item?id=46964661</link><dc:creator>jostkolega</dc:creator><comments>https://news.ycombinator.com/item?id=46964661</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46964661</guid></item><item><title><![CDATA[New comment by jostkolega in "Ask HN: What are you working on? (February 2026)"]]></title><description><![CDATA[
<p>Running security audits on open source repos with a tool we've built and reporting what I find to maintainers. Mostly infrastructure stuff — vector
databases, LLM tooling, secrets managers. Been doing responsible
disclosure and submitting fixes which are all autogenerated. Surprisingly high acceptance rate so far, which is encouraging. Working on automating more
of the test process...</p>
]]></description><pubDate>Tue, 10 Feb 2026 18:29:07 +0000</pubDate><link>https://news.ycombinator.com/item?id=46964503</link><dc:creator>jostkolega</dc:creator><comments>https://news.ycombinator.com/item?id=46964503</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46964503</guid></item><item><title><![CDATA[New comment by jostkolega in "Yikes – Security scanner for AI-generated code"]]></title><description><![CDATA[
<p>Semgrep's a solid choice for this. The stuff you're catching - secrets, SQLi, 
weak hashing-  is where pattern matching shines.<p>The tricky part with LLM-generated code is when it's syntactically fine but 
semantically broken. Stuff like:<p>- auth logic that checks user.role but also has a `req.query.admin === 'true'` 
  fallback because the model left debug code in<p>- JWT validation that calls verify() but passes `algorithms: ['none']` or 
  disables signature checking — the code <i>looks</i> right<p>- async TOCTOU bugs where permission check and action aren't atomic because 
  the LLM wrote it like sync code<p>None of these match simple patterns. You need dataflow analysis to 
catch them reliably.<p>Curious if you're thinking about that for the paid tier, or keeping it 
pattern-based to stay fast?</p>
]]></description><pubDate>Tue, 03 Feb 2026 12:15:22 +0000</pubDate><link>https://news.ycombinator.com/item?id=46870029</link><dc:creator>jostkolega</dc:creator><comments>https://news.ycombinator.com/item?id=46870029</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46870029</guid></item><item><title><![CDATA[New comment by jostkolega in "Show HN: Kekkai – Interactive security triage in the terminal"]]></title><description><![CDATA[
<p>+1 on triage being the real problem. Question, when Semgrep surfaces something ambiguous, lets say a SQL query that looks parameterized but the ORDER BY is built elsewhere, what does reviewing that actually look like? I'm wondering how much context you get before needing to jump out to the codebase.</p>
]]></description><pubDate>Tue, 03 Feb 2026 11:35:49 +0000</pubDate><link>https://news.ycombinator.com/item?id=46869665</link><dc:creator>jostkolega</dc:creator><comments>https://news.ycombinator.com/item?id=46869665</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46869665</guid></item></channel></rss>