Dependency Health
Audit dependency health, upgrade risk, security alerts, and maintenance load from the manifests, lock files, advisory reports, and release history the user supplies. Separates direct from transitive and runtime from build or dev exposure, classifies the version gap by semver jump, checks each advisory against the resolved version and its fix path, rates maintenance signals (active, slow, stale, abandoned), applies hard gates before a points score, batches upgrades by risk, estimates ongoing maintenance load, and recommends patch now, schedule, pin, replace, remove, or accept with an expiry. Use when someone asks for a dependency audit, whether packages are outdated or abandoned, how risky an upgrade is, what to do about a pile of security alerts, or how much upkeep dependencies cost. Do not use for turning findings into a ranked backlog (use maintenance-backlog), a cloud infrastructure review (use audit-cloud-infrastructure), or vetting an imported skill's source (use import-provenance-checker).