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
1965.2
3997.7 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.3libyears removed where work was done
Net+60.5further behind, after upstream releases
vitejs/vite−0.7
vuejs/core−0.6

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 repos6 versions
@types/node8 repos8 versions
prettier8 repos7 versions
vitest7 repos6 versions
eslint6 repos6 versions
rollup6 repos6 versions
lint-staged6 repos4 versions
postcss6 repos4 versions
2 repositories are running a runtime that is past its end-of-life date.

Frameworks

1557.8 libyears
vercel/next.js626 direct, 4226 transitive · end-of-life runtime
D 44
facebook/react112 direct, 1094 transitive · end-of-life runtime · 3 PRs waiting
D 54
angular/angular462 direct, 2690 transitive
B 80
sveltejs/svelte60 direct, 449 transitive · 3 PRs waiting
B 82
vuejs/core120 direct, 576 transitive · 7 PRs waiting
A 92

Tooling

343.9 libyears
storybookjs/storybook908 direct, 2898 transitive
C 55
vitejs/vite413 direct, 1296 transitive · 2 PRs waiting
A 94

Backend

63.4 libyears
prisma/prisma1972 direct, 1310 transitive · 6 PRs waiting
B 74
nestjs/nest159 direct, 1459 transitive · 4 PRs waiting
A 97
expressjs/express44 direct, 0 transitive · declared ranges only
A 87
See your own repositories like thisFive private repositories free, public ones always. Nothing is written to your code.
Start free with GitHubnpx libyears

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>.