endor-upgrade-impact

To find the safest dependency upgrade path, this Skill uses pre-computed Endor Labs data to surface versions that fix vulnerabilities with minimal risk and minimal code changes. It returns a concise recommendation evaluating upgrade risk, fix coverage, and version availability.

Checking breaking changes from upgrading a package involves analyzing its impact on security, compatibility, and behavior. This Skill uses pre-computed Endor Labs data to assess these factors and determine if an upgrade is worth it or introduces unnecessary risk.

You do not need to run a new scan to analyze dependency upgrade risk. This Skill uses pre-computed Endor Labs data from prior project scans to quickly evaluate upgrade risk and surface the best version recommendations without active scanning.

You cannot use this to just check for vulnerabilities in your dependencies. This Skill is specifically designed to analyze upgrade impact and find safe paths, not to perform general vulnerability checks or apply fixes to existing dependency versions.

Evaluating whether a dependency upgrade is worth it is done by checking pre-computed data fields like is_best, worth_it, and upgrade_risk. The Skill prioritizes upgrades that fix vulnerabilities while minimizing risk and code changes, returning a clear rationale.