<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Open-Code-Review on SoloSoft</title><link>https://www.solosoft.dev/tags/open-code-review/</link><description>Recent content in Open-Code-Review on SoloSoft</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 14 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.solosoft.dev/tags/open-code-review/index.xml" rel="self" type="application/rss+xml"/><item><title>Open Code Review Cites a File and a Line for Every Security Claim — Except the Path That Reaches Your CI</title><link>https://www.solosoft.dev/post/open-code-review-assurance-case-audit/</link><pubDate>Sat, 14 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.solosoft.dev/post/open-code-review-assurance-case-audit/</guid><description>&lt;p&gt;Most AI coding tools ship a README that says &amp;ldquo;secure by design&amp;rdquo; and stop there. Alibaba&amp;rsquo;s Open Code Review (&lt;code&gt;ocr&lt;/code&gt;) ships a &lt;code&gt;ASSURANCE_CASE.md&lt;/code&gt; — 120 lines that map &lt;a href="https://ieeexplore.ieee.org/document/1451869"&gt;Saltzer &amp;amp; Schroeder&amp;rsquo;s design principles&lt;/a&gt;, the OWASP Top 10 and the CWE/SANS Top 25 onto named files, functions and line numbers. It is the kind of artifact normally written for an enterprise procurement review, published in public.&lt;/p&gt;
&lt;p&gt;That makes it testable in a way marketing copy never is. So I downloaded the release binary, stood up a mock LLM endpoint, and drove the thing with adversarial tool calls. Twelve of the claims hold up under live testing — better than I expected. One does not, and it happens to be the one whose output lands in your CI pipeline.&lt;/p&gt;</description></item></channel></rss>