<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Claude-Code-Slack-Channel on Start AI Tools - Presented by Intent Solutions</title><link>https://startaitools.com/tags/claude-code-slack-channel/</link><description>Recent content in Claude-Code-Slack-Channel on Start AI Tools - Presented by Intent Solutions</description><generator>Hugo</generator><language>en-US</language><copyright>Intent Solutions. All rights reserved.</copyright><lastBuildDate>Thu, 14 May 2026 07:05:55 -0600</lastBuildDate><atom:link href="https://startaitools.com/tags/claude-code-slack-channel/index.xml" rel="self" type="application/rss+xml"/><item><title>Transitive CVE Clearance: The Dual-Layer Pattern</title><link>https://startaitools.com/posts/transitive-cve-clearance-dual-layer-pattern/</link><pubDate>Wed, 13 May 2026 08:00:00 -0500</pubDate><guid>https://startaitools.com/posts/transitive-cve-clearance-dual-layer-pattern/</guid><description>&lt;p&gt;You bump a direct dependency to pull in a patched transitive. &lt;code&gt;bun audit&lt;/code&gt; goes green. The lockfile is committed. Two weeks later, someone does a clean install on a fresh machine, and the vulnerable transitive comes back. This is the transitive CVE trap, and it catches teams with the first move alone.&lt;/p&gt;
&lt;p&gt;The v0.9.1 release of claude-code-slack-channel cleared 6 high-severity CVEs in axios and fast-uri. It required two distinct moves: first, bump the direct deps that pull the patched transitives. Second, pin those transitives at the top-level overrides block so the lockfile cannot regress on the next &lt;code&gt;bun install&lt;/code&gt;. Both moves are mandatory. Here&amp;rsquo;s why.&lt;/p&gt;</description></item></channel></rss>