<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Code Quality on Arivu</title>
		<link>https://arivu.app/tags/code-quality/</link>
		<description>Recent content in Code Quality on Arivu</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sun, 08 Mar 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://arivu.app/tags/code-quality/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Automated Security, Testing, and Code Quality</title>
				<link>https://arivu.app/chronicle/security-quality-automation/</link>
				<pubDate>Sun, 08 Mar 2026 00:00:00 +0000</pubDate>
				<guid>https://arivu.app/chronicle/security-quality-automation/</guid>
				<description>&lt;p&gt;&lt;strong&gt;Historical note, July 2026:&lt;/strong&gt; This post reflects the automation used by the earlier Python and JavaScript stack. The current Go-based app uses a different, smaller dependency surface and validation workflow. The product-level commitment still stands: automated checks should catch security, quality, and regression issues before release.&lt;/p&gt;&#xA;&lt;p&gt;With the codebase now open source, we invested in the automation that keeps it healthy. This update adds continuous integration pipelines, automated dependency monitoring, static analysis, and a frontend test suite - the kind of infrastructure that catches problems before they reach you.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
