<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Revelara</title><link>https://revelara.ai/tags/revelara/</link><description>Recent content on Revelara</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 19 Jul 2026 08:00:00 -0700</lastBuildDate><atom:link href="https://revelara.ai/tags/revelara/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Scan a Codebase for Reliability Risks with rvl-cli</title><link>https://revelara.ai/blog/install-rvl-cli-first-risk-register/</link><pubDate>Sun, 19 Jul 2026 08:00:00 -0700</pubDate><guid>https://revelara.ai/blog/install-rvl-cli-first-risk-register/</guid><description>&lt;p&gt;Clone a repo you&amp;rsquo;ve never scanned, install the Revelara CLI, run one scan, and read a ranked list of the reliability risks in that codebase. Budget about fifteen minutes end to end, and know that your hands-on part is a fraction of it. The scan does analysis, reading your code against a controls catalog with expert lenses, and real analysis takes longer than a grep. Kick it off, click through the permissions prompts, and load the risk register. This post is a walkthrough, using a public repo you can clone yourself.&lt;/p&gt;</description></item></channel></rss>