09-dependencies

Map internal and external dependencies with risk scoring and EOL checks.

1|Updated Apr 11, 2026

Search Tags:#architecture #dependencies #code-analysis #risk-analysis #circular-dependency #fan-in

Ready to run

npx skills add https://github.com/vishalkhondre/unearth --skill 09-dependencies

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: 09-dependencies
Source: https://github.com/vishalkhondre/unearth/tree/main/skills/09-dependencies
Command: npx skills add https://github.com/vishalkhondre/unearth --skill 09-dependencies

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maps internal component dependencies (business-to-business, business-to-technical), external package dependencies with version and risk analysis, and shared library coupling. Identifies critical coupling points, EOL frameworks, version conflicts, and dead dependencies. Use after 08-patterns to complete the Knowledge stage before Assessment.

Core Features & Use Cases

Build internal business-to-business and business-to-technical dependency maps across containers.
Inventory external packages with risk indicators (EOL, version conflicts, deprecated packages) and identify dead dependencies.
Highlight critical coupling points and guide modernization planning.

Quick Start

Run the 09-dependencies skill after the 08-patterns step to generate the full dependencies report.

Frequently Asked Questions about 09-dependencies

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I map internal component dependencies across multi-container architectures?▼

To map internal component dependencies across multi-container architectures, you can generate business-to-business and business-to-technical dependency maps. This highlights critical coupling points to guide your modernization planning.

How do I detect circular dependencies and perform fan-in analysis?▼

Detecting circular dependencies and performing fan-in analysis requires upstream component inventories. The process enforces these checks alongside risk scoring to identify critical coupling points and assess structural risk across the stack.

What is the best way to inventory external packages and identify dead dependencies?▼

Inventorying external packages and identifying dead dependencies involves scanning your libraries for version conflicts, deprecated packages, and EOL frameworks. This generates risk indicators to highlight unused or dead dependencies.

Can I use dependency risk analysis for legacy modernization scenarios?▼

Yes, dependency risk analysis applies to modernization scenarios by inventorying components, packages, and shared libraries. It assesses risk across the stack using EOL checks and risk scoring to support your planning.

Do I need an upstream component inventory before analyzing shared library coupling?▼

Yes, you need an upstream component inventory before analyzing shared library coupling. The dependency analysis enforces requirements for upstream inventories, fan-in analysis, and risk scoring to accurately identify critical coupling points.

Why does dependency analysis require running after the pattern identification step?▼

Dependency analysis runs after the pattern identification step to complete the Knowledge stage before Assessment. Running the 09-dependencies step after 08-patterns ensures you generate the full dependencies report with accurate risk scoring.