Hi Product Hunt. I maintain a lot of client codebases and could never answer "how far behind are we?" in one number. Counting outdated packages doesn't work: one updated last week and one pinned in 2019 both count as one. libyears measures time instead. One libyear is one year of release time between the version you have installed and the newest that exists; a portfolio adds up. Here it is on ten public repositories you know, scanned daily: https://libyears.com/showcase It reads every repository you maintain through a GitHub App with Contents: read only, scores each one on freshness, known vulnerabilities, runtime end-of-life and maintenance signals, keeps the history, and produces a per-client report you can send with the invoice. It never writes to your repositories or opens pull requests; Renovate and Dependabot do that, and this tells you which of the open ones matter. Private package names never leave your account. Five private repositories are free, and npx libyears works offline on a checkout with no account. Ask me anything about the scoring; every number on a repository page explains itself.

libyears

How far behind are your dependencies? Measured in years

How far behind are your dependencies? Measured in years