<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CRAP on Unbound Force</title><link>https://unboundforce.dev/tags/crap/</link><description>Recent content in CRAP on Unbound Force</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright (c) 2025-2026 Unbound Force</copyright><lastBuildDate>Sun, 23 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://unboundforce.dev/tags/crap/index.xml" rel="self" type="application/rss+xml"/><item><title>Gaze Baseline Comparison — Per-Function CRAP Regression Detection</title><link>https://unboundforce.dev/blog/gaze-baseline-comparison/</link><pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate><guid>https://unboundforce.dev/blog/gaze-baseline-comparison/</guid><description>&lt;h2 id="the-850-line-comparison-script-problem"&gt;The 850-Line Comparison Script Problem&lt;/h2&gt;
&lt;p&gt;Organizations adopting Gaze for CRAP score analysis faced a gap: Gaze could compute per-function CRAP scores for a single run, but it had no way to compare those scores against a previous baseline. Detecting regressions — a function whose complexity increased or whose coverage dropped — required external tooling. The only option was org-infra&amp;rsquo;s reusable GitHub Actions workflow, which embedded an 850-line bash/Python comparison script to diff two JSON reports and flag regressions.&lt;/p&gt;</description></item></channel></rss>