Map internal and external dependencies with risk scoring and EOL checks.
npx skills add https://github.com/vishalkhondre/unearth --skill 09-dependencies
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
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.
Run the 09-dependencies skill after the 08-patterns step to generate the full dependencies report.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
tianzecnAnalyze software architecture using AST structural analysis to map layers and dependencies.
s3nex-comAudit dependency health across services with CVE triage and SBOM reviews.
quangphu1912Identify technologies, frameworks, and libraries in a codebase.
mvillmowDetect security vulnerabilities in code and dependencies with static analysis.
