dependency-analyzer

Fetch npm and endoflife.date data to report EOL status and compatibility for JavaScript libraries.

Updated Nov 30, 2025
One-click install
npx skills add https://github.com/snhrm/claude-plugin --skill dependency-analyzer-snhrm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-analyzer
Source: https://github.com/snhrm/claude-plugin/tree/main/plugin/skills/dependency-analyzer
Command: npx skills add https://github.com/snhrm/claude-plugin --skill dependency-analyzer-snhrm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly determine end-of-life and compatibility risks for libraries, enabling proactive upgrade planning and reduced maintenance surprises.

Core Features & Use Cases

  • EOL Status Retrieval: Fetches endoflife.date and npm registry data to assess support timelines.
  • Compatibility Checks: Analyzes engines, peerDependencies, and version ranges to identify potential conflicts.
  • Migration Guidance: Provides upgrade recommendations and pointers to migration guides.
  • Use Case: When planning to upgrade a project from React 18.x to 19.x, this Skill highlights required changes and timelines.

Quick Start

Analyze library 'react' version '18.2.0' and return a recommended upgrade plan.

Frequently Asked Questions about dependency-analyzer

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

FAQPage Schema
How do I check if a Node.js library version is end-of-life before upgrading?

End-of-life status identifies when a library stops receiving support. This Skill fetches EOL timelines from endoflife.date and the npm registry, reporting support windows and deprecation dates so you can plan upgrades safely and avoid unsupported versions.

Can I determine Node.js engine and peer dependency compatibility for a library upgrade?

Yes. This Skill analyzes engines and peerDependencies constraints from npm package metadata, identifying conflicts between your target library version and your project's runtime or dependent packages, enabling you to catch incompatibilities before deployment.

What's the best way to audit React or Next.js dependency risks before a major version bump?

Dependency audits assess EOL status, version ranges, and compatibility requirements to surface risks. This Skill structures that analysis by fetching package data and LTS timelines, then outputs actionable upgrade recommendations and migration guidance for safe transitions.

How do I get upgrade recommendations and migration timelines for JavaScript libraries?

Upgrade planning requires understanding EOL dates, compatibility constraints, and next-step versions. This Skill fetches and parses npm registry and endoflife.date data, then outputs a structured schema with support timelines, compatibility notes, and recommended upgrade paths.

Does this work with tooling like webpack, TypeScript, or other Node.js ecosystem packages?

Yes. This Skill targets JavaScript ecosystem libraries—Node.js, React, Next.js, and related tooling—parsing standard npm package metadata to assess compatibility and EOL status across the entire dependency tree.

What happens if a library has no published end-of-life data or non-standard version schemes?

Data availability depends on endoflife.date coverage and npm registry publishing practices. This Skill reports what data is available; if EOL dates are missing or version formats are non-standard, the output flags gaps so you can research alternatives or contact maintainers directly.