4 ms·
My current employer publishes "staleness" metrics at the project level. It's imperfect because it weights all the dependencies the same, but it's better than n
by coredog64 11mo ago
My current employer publishes "staleness" metrics at the project level. It's imperfect because it weights all the dependencies the same, but it's better than nothing.
- m000 11mo agoI wonder, are there tools to help you automate this? I.e. to assign a value to the staleness of each package instead of simple "oudated" boolean, and also a weight to each package. E.g. something like: pkg_staleness = (1 * missed_patch + 5 * missed_minor + 10 * missed_major) * (month_diff(installed_release_date, latest_release_date)/2)^2 proj_staleness = sum(pkg.staleness * pkg.weight for pkg in all_packages)
- decasia 11mo agoMy current org uses this: https://libyear.com/ https://libyear.com/