Deadpendency assesses your repository dependencies for project health. A healthy dependency is being actively committed to, by multiple maintainers with regular package releases. Deadpendency checks your dependencies remain healthy over time and will fail the check if a dependency has become unhealthy. See an example report.
In modern development, there is constant platform and dependency churn. The best solution is to proactively keep dependencies up to date. Thankfully, there are great tools to assist with this such as Dependabot.
Dependabot and the like work great when dependencies are actively being maintained and updates released. However, sometimes dependencies become inactive or deprecated. In this case, users of the dependency are stuck on an unchanging version. This causes the same problems as not updating dependencies, however dependency update tools will not report on this issue.
Deadpendency checks your software dependencies are still active and healthy projects. It runs on every git push, keeping you aware of your dependency project health over time. Each push produces a report giving a quick snapshot of dependency health.
Visit Deadpendency website.