<?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 AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/dependency-management/</link><description>Recent content in Dependency Management on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 20 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/dependency-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Setting Up Your AI Reliability Toolkit: Environment &amp;amp; Essentials</title><link>https://ai-blog.noorshomelab.dev/ai-reliability-guide-2026/ai-reliability-toolkit-setup/</link><pubDate>Fri, 20 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/ai-reliability-guide-2026/ai-reliability-toolkit-setup/</guid><description>&lt;h2 id="introduction-laying-the-foundation-for-reliable-ai"&gt;Introduction: Laying the Foundation for Reliable AI&lt;/h2&gt;
&lt;p&gt;Welcome back, future AI reliability engineer! In our previous chapter, we explored the critical importance of ensuring AI systems are robust, safe, and trustworthy. We discussed why AI evaluation and guardrails aren&amp;rsquo;t just good practices, but essential components for any AI system aiming for production readiness.&lt;/p&gt;
&lt;p&gt;Now, it&amp;rsquo;s time to roll up our sleeves and get practical. Before we can dive into the exciting world of prompt testing, hallucination detection, or designing sophisticated guardrails, we need a solid foundation: a well-configured development environment. Think of it like a chef preparing their kitchen before cooking a gourmet meal – the right tools and a clean workspace are crucial for success.&lt;/p&gt;</description></item><item><title>Chapter 9: Security Misconfigurations &amp;amp; Vulnerable and Outdated Components</title><link>https://ai-blog.noorshomelab.dev/web-security-hacker-dev-2026/misconfigurations-vulnerable-components/</link><pubDate>Sun, 04 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/web-security-hacker-dev-2026/misconfigurations-vulnerable-components/</guid><description>&lt;h2 id="introduction-the-hidden-dangers-in-your-setup"&gt;Introduction: The Hidden Dangers in Your Setup&lt;/h2&gt;
&lt;p&gt;Welcome back, future security champion! In our journey through web application security, we&amp;rsquo;ve explored how attackers think and how to guard against common injection flaws and authentication issues. Now, it&amp;rsquo;s time to tackle two equally critical, yet often overlooked, areas: &lt;strong&gt;Security Misconfigurations&lt;/strong&gt; and &lt;strong&gt;Vulnerable and Outdated Components&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;These aren&amp;rsquo;t flashy &amp;ldquo;hacking techniques,&amp;rdquo; but rather systemic weaknesses that can leave your carefully built applications wide open. Imagine building a high-security vault, but leaving the blueprints on the front desk (misconfiguration) or using a lock that&amp;rsquo;s known to be easily picked because it&amp;rsquo;s an old model (vulnerable component). That&amp;rsquo;s essentially what these vulnerabilities represent.&lt;/p&gt;</description></item><item><title>Advanced Injection-JS Features</title><link>https://ai-blog.noorshomelab.dev/injection-js-guide-chapters/advanced-injection-js-features/</link><pubDate>Sat, 25 Oct 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/injection-js-guide-chapters/advanced-injection-js-features/</guid><description>&lt;h2 id="4-advanced-injection-js-features"&gt;4. Advanced Injection-JS Features&lt;/h2&gt;
&lt;p&gt;You&amp;rsquo;ve mastered the fundamentals and hierarchies. Now, let&amp;rsquo;s explore some of the more advanced features of Injection-JS that allow for highly flexible and powerful dependency management in complex applications.&lt;/p&gt;
&lt;h3 id="multi-providers-multi-true"&gt;Multi-Providers (&lt;code&gt;multi: true&lt;/code&gt;)&lt;/h3&gt;
&lt;p&gt;Sometimes, you don&amp;rsquo;t want to provide a single instance of a service, but rather &lt;em&gt;multiple&lt;/em&gt; instances or values associated with a single injection token. This is where multi-providers come in handy. When &lt;code&gt;multi: true&lt;/code&gt; is used in a provider, instead of replacing previous definitions for that token, it &lt;em&gt;adds&lt;/em&gt; to a collection. When the token is resolved, you get an array of all registered values.&lt;/p&gt;</description></item></channel></rss>