libyears

Ten repositories everyone knows, on one screen

This is the overview page every account gets, pointed at public repositories instead of yours. Open a row to see its direct dependencies, how far each has drifted, and what is dangerous today.

libyears behind
1978.4
4020.9 weighted for breaking changes
Needs attention
1
0 critical, 1 high
Quick wins
0
fixed without a major bump
Median health
81
10 repos, 3 groups

Last 30 days

10 repositories measured
Paid off1.2libyears removed where work was done
Net+51.7further behind, after upstream releases
angular/angular−1.2

Shared across repositories

One upgrade, several repositories. Where the version count is higher than one, they have drifted apart and the upgrade is really several.

typescript9 repos7 versions
@types/node8 repos8 versions
vitest8 repos7 versions
prettier8 repos7 versions
esbuild7 repos3 versions
eslint6 repos6 versions
rollup6 repos6 versions
ws6 repos5 versions
1 repository is running a runtime that is past its end-of-life date.

Frameworks

1570.2 libyears

Tooling

342.7 libyears

Backend

65.5 libyears
See your own repositories like thisFive private repositories free, public ones always. Nothing is written to your code.

Public repositories, read from their manifests and lockfiles through the GitHub API and rescanned daily by the same pipeline every account uses. They belong to their maintainers, not to a customer of ours. Versions come from lockfiles, release dates from the npm registry, advisories from OSV.

Looking for one package rather than one repository? Every npm package has a page at /p/<name>.