Analyzes project dependencies and provides contextual data to assess upgrade impact.

Supports: npm (package.json) and pip (requirements.txt) only. Other package managers (Poetry, Pipenv, Cargo, Go modules, Maven, Gradle, Composer, NuGet, etc.) are not supported.

Returns for each dependency: name, current version, latest version, status, changelog_content (actual release notes or explanatory message), description, and release_date.

When to use this tool:

• User asks about dependency versions/updates in a specific project

• User requests dependency health check or audit

• Before suggesting upgrades that require inspecting actual project dependencies

How to analyze results:

1. Use changelog_content to identify specific changes, bug fixes, breaking changes

2. State that assessment is limited if changelog could not be fetched

3. Direct user to source URL if mentioned in changelog_content

4. Do not infer changes not explicitly stated in changelog_content

5. Use description and release_date to assess maturity/stability

6. Consider major version gaps as potential breaking change indicators

Provide recommendations (low/medium/high impact) based on risk, scope, and maintenance implications—not just version differences.