Developer Experience
Dependency Freshness Calculator
Enter dependency count, major/minor version lag counts, and average age to compute libyear debt, security risk tier, and update prioritization.
No data is transmitted — everything runs locallyTool
Example — 45 deps · 8 outdated major · 15 outdated minor · 18mo avg age
Outdated major
8/45
breaking changes available
Outdated minor
15/45
features + fixes available
Libyear debt
0.5 yr
weighted age debt
Freshness score
12/100
Critical
About this tool
Dependency Freshness Calculator
The Dependency Freshness Calculator computes libyear debt, security risk from version lag, and update prioritization from dependency age and version statistics.
• Calculate libyear score for a quarterly dependency health report
• Prioritize dependency updates by security risk from major version lag
• Build a business case for dedicated dependency update sprints
• Estimate the effort required to bring dependencies current across a codebase
Affiliate disclosure
Uptime, incident, and on-call management. Better Stack provides status pages, incident management, and on-call scheduling for engineering teams.
View options with Better Stack
External site · Independent provider · We may receive a commission · Not a recommendation
FAQ
What does this tool tell you?
The Dependency Freshness Calculator computes libyear debt, security risk from version lag, and update prioritization from dependency age and version statistics.
What affects the result most?
Dependency age: months since current version was released — older = more likely to have known CVEs. Version lag: how many versions behind current is the installed version?. Libyear: sum of years behind across all dependencies — 'tech debt in library-years'.
How should I use the result?
The calculation is deterministic — the same inputs always produce the same output — so the most useful workflow is to vary one input at a time and see which factor moves the result most. That tells you where to focus your attention before committing to a decision.