A Deep Dive into Measuring Dependency Freshness with LibYear
summary
LibYear measures how many years each dependency lags and sums them to a project score; a real example shows pyspider at ~121 LibYears today. A history-aware tool called libmetrics (and a proof‑of‑concept service freshly) computes LibYear over time and plots spikes — one 2019 surge tied to Python 2.7 EOL. The freshly.io demo supports requirements.txt, shows netbox keeping packages under ~2 years, and plans private repo and security‑risk metrics.
AI-written summary · about
chapters (11)
- 0:00Introduction and background
- 3:20Why dependencies get outdated
- 5:02What is dependency freshness
- 9:16Introducing LibYear
- 11:23Measuring LibYear manually
- 12:29Tracking LibYear over time
- 13:30Introducing Freshly tool
- 17:26Freshly's future and vision
- 20:56Other dependency freshness measures
- 21:58Automating dependency updates
- 23:02Q&A and closing
related talks
38mDependency Management: The Cause of—and Solution to—All Supply...
32mA Decade Of Infosec Tools
05mDependency Demons
28mTowards Automated Updates of Software Dependencies
39mThe JupyterLab Extension Ecosystem- Trends from PyPI +GitHub
37mKeep Your Dependencies in Check
19mExtending the Error Budget Model to Security and Feature Freshness
08mAll About Dependencies