<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: adityacs50-lab</title>
    <description>The latest articles on DEV Community by adityacs50-lab (@adityacs50lab).</description>
    <link>https://dev.to/adityacs50lab</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3657601%2F877696a6-80ea-40e5-99a6-b6e037216fc1.png</url>
      <title>DEV Community: adityacs50-lab</title>
      <link>https://dev.to/adityacs50lab</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/adityacs50lab"/>
    <language>en</language>
    <item>
      <title>I open sourced my API auto repairing tool for free</title>
      <dc:creator>adityacs50-lab</dc:creator>
      <pubDate>Thu, 24 Sep 2026 18:14:22 +0000</pubDate>
      <link>https://dev.to/adityacs50lab/i-open-sourced-my-api-auto-repairing-tool-for-free-49i1</link>
      <guid>https://dev.to/adityacs50lab/i-open-sourced-my-api-auto-repairing-tool-for-free-49i1</guid>
      <description>&lt;p&gt;Building and maintaining APIs can be exhausting. Between schema changes, breaking updates, and unexpected payload mismatches, things constantly break in production. That is why I built and open-sourced &lt;strong&gt;&lt;a href="https://github.com/adityacs50-lab/Repairo" rel="noopener noreferrer"&gt;Repairo&lt;/a&gt;&lt;/strong&gt;—a free, automated tool designed to detect and auto-repair API issues before they cause downstream failures.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why I Built Repairo
&lt;/h2&gt;

&lt;p&gt;Modern microservices architectures rely heavily on APIs communicating seamlessly. However, minor changes in data contracts often result in unhandled exceptions or failed requests. Instead of manually writing patches or dealing with late-night debugging sessions, Repairo intercepts failing requests, analyzes the schema divergence, and applies safe auto-corrections on the fly.&lt;/p&gt;

&lt;h2&gt;
  
  
  Key Features
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Automated Schema Healing:&lt;/strong&gt; Detects discrepancies in incoming/outgoing payloads and maps them to expected types.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Zero-Downtime Patching:&lt;/strong&gt; Keeps services running smoothly without requiring an immediate manual deployment for minor drift issues.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Lightweight &amp;amp; Extensible:&lt;/strong&gt; Built to integrate easily into existing API gateways and middleware pipelines.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Get Started
&lt;/h2&gt;

&lt;p&gt;The project is completely open source. You can check out the repository, inspect the code, or contribute over at the &lt;strong&gt;[Repairo GitHub Repository] &lt;a href="https://github.com/adityacs50-lab/Repairo" rel="noopener noreferrer"&gt;https://github.com/adityacs50-lab/Repairo&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Contributions, feature requests, and feedback are always welcome!&lt;/p&gt;

</description>
      <category>ai</category>
      <category>api</category>
      <category>tooling</category>
      <category>devops</category>
    </item>
    <item>
      <title>Repairo: Stop Breaking Builds When Vendor OpenAPI Specs Update</title>
      <dc:creator>adityacs50-lab</dc:creator>
      <pubDate>Fri, 18 Sep 2026 19:06:54 +0000</pubDate>
      <link>https://dev.to/adityacs50lab/repairo-stop-breaking-builds-when-vendor-openapi-specs-update-2h1o</link>
      <guid>https://dev.to/adityacs50lab/repairo-stop-breaking-builds-when-vendor-openapi-specs-update-2h1o</guid>
      <description>&lt;h2&gt;
  
  
  The Problem
&lt;/h2&gt;

&lt;p&gt;Dependabot and Renovate are great at bumping version numbers in your &lt;code&gt;package.json&lt;/code&gt;, but they won't fix your code when a vendor introduces a breaking change.&lt;/p&gt;

&lt;p&gt;When OpenAI or Stripe renames a parameter, drops a field, or updates a base path, your CI pipeline breaks or—worse—silent runtime errors slip into production. You end up manually searching the codebase, editing call sites by hand, or pasting broad context into AI tools hoping for an accurate fix.&lt;/p&gt;




&lt;h2&gt;
  
  
  What is Repairo?
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://github.com/adityacs50-lab/Repairo" rel="noopener noreferrer"&gt;Repairo&lt;/a&gt; is an open-source tool that continuously monitors OpenAPI specs for breaking changes, maps the exact impact across your codebase using compiler-grade AST parsing, and automatically generates compile-checked pull requests to fix the call sites.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Deterministic AST Transforms:&lt;/strong&gt; Where the spec change is unambiguous (like &lt;code&gt;max_tokens&lt;/code&gt; → &lt;code&gt;max_output_tokens&lt;/code&gt;), fixes are applied deterministically via Abstract Syntax Tree (AST) manipulation rather than probabilistic guessing.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Typecheck &amp;amp; Syntax Validated:&lt;/strong&gt; Before proposing any changes, fixes are validated using TypeScript/JavaScript type-checking or Python/Go syntax checks.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Human-in-the-Loop:&lt;/strong&gt; Repairo opens a clean, reviewable PR with full change evidence—it never auto-merges.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Quick Start (CLI)
&lt;/h2&gt;

&lt;p&gt;No signup or config file required. Run a quick scan against your codebase:&lt;/p&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;
bash
npx repairo-cli scan ./src --vendors stripe,openai,supabase

Or test deterministic repairs locally:

# Install CLI globally
npm install -g repairo-cli

# Scan and run a dry-run repair
repairo check --vendors stripe,openai --target ./src
repairo repair --dry-run --target ./src

Links &amp;amp; Feedback
GitHub Repo: adityacs50-lab/Repairo

Live Web Demo: heyrepairo.in/

Give it a spin on your project, and let us know what vendors or language AST mappings you'd like to see supported next!
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

</description>
      <category>javascript</category>
      <category>typescript</category>
      <category>webdev</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
