<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Shift Left on Saurabh Chaubey</title>
    <link>https://saurabh-chaubey.com/tags/shift-left/</link>
    <description>Recent content in Shift Left on Saurabh Chaubey</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 10 Mar 2026 10:00:00 +0000</lastBuildDate><atom:link href="https://saurabh-chaubey.com/tags/shift-left/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Shifting Way Left: Integrating Trivy Security Scanning Into Your IDE AI Agent</title>
      <link>https://saurabh-chaubey.com/post/devops/shifting-way-left-integrating-trivy-security-scanning-into-ide-ai-agent/</link>
      <pubDate>Tue, 10 Mar 2026 10:00:00 +0000</pubDate>
      
      <guid>https://saurabh-chaubey.com/post/devops/shifting-way-left-integrating-trivy-security-scanning-into-ide-ai-agent/</guid>
      <description>How to catch vulnerabilities, secrets, and container image issues before your code ever leaves the IDE — and why that changes everything.
The Problem Nobody Talks About Here is a scenario every developer knows: you push your code, open a pull request, watch the CI pipeline spin up, wait several minutes, and then — red. A security scanner found a critical CVE in a transitive dependency, or worse, a leaked API key in a properties file.</description>
    </item>
    
  </channel>
</rss>
