<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dependency-Management on krash.dev</title><link>https://krash.dev/tags/dependency-management/</link><description>Recent content in Dependency-Management on krash.dev</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 14 Aug 2026 08:29:09 +0530</lastBuildDate><atom:link href="https://krash.dev/tags/dependency-management/rss.xml" rel="self" type="application/rss+xml"/><item><title>Handling Deprecated Dependencies In Your Project</title><link>https://krash.dev/posts/handling-deprecated-dependencies/</link><pubDate>Tue, 07 Nov 2023 00:00:00 +0000</pubDate><guid>https://krash.dev/posts/handling-deprecated-dependencies/</guid><description>&lt;p&gt;&lt;em&gt;&lt;strong&gt;Disclaimer&lt;/strong&gt;: Just a heads up, while we&amp;rsquo;re diving into ways to tackle the problem of dependency depreciation, there&amp;rsquo;s no one-size-fits-all solution here. It&amp;rsquo;s a bit of a wild ride dealing with supply chain security and those pesky deprecated dependencies, so don&amp;rsquo;t expect a quick fix!&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The issue of using deprecated dependencies has persisted for quite some time, and it&amp;rsquo;s gaining increased attention. Many projects continue to incorporate deprecated dependencies.&lt;/p&gt;
&lt;p&gt;I was inspired to write this blog after coming across &lt;a href="https://www.linkedin.com/posts/rorym_softwaresupplychainsecurity-activity-7127600960364797954-rAJE/" target="_blank" rel="noopener noreferrer"&gt;a LinkedIn post by Rory McCune&lt;/a&gt; and several other posts over the past few weeks.&lt;/p&gt;</description></item></channel></rss>