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
1861.9
3794.6 weighted for breaking changes
Needs attention
1
0 critical, 1 high
Quick wins
0
fixed without a major bump
Median health
87
10 repos, 3 groups

Last 30 days

No repository has been scanned twice yet, so there is no trend to report. This fills in after the second scan.

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
prettier8 repos6 versions
eslint7 repos7 versions
vitest7 repos6 versions
rollup6 repos6 versions
lint-staged6 repos5 versions
postcss6 repos3 versions
2 repositories are running a runtime that is past its end-of-life date.

Frameworks

1501.0 libyears
vercel/next.js618 direct, 4412 transitive · end-of-life runtime
D 46
facebook/react113 direct, 1098 transitive · end-of-life runtime
C 55
angular/angular432 direct, 2895 transitive
B 80
sveltejs/svelte60 direct, 449 transitive · 3 PRs waiting
A 87
vuejs/core121 direct, 560 transitive · 12 PRs waiting
A 92

Tooling

330.1 libyears
storybookjs/storybook890 direct, 2842 transitive
C 55
vitejs/vite404 direct, 1364 transitive · 2 PRs waiting
A 94

Backend

30.8 libyears
prisma/prisma1729 direct, 1271 transitive · 3 PRs waiting
A 88
nestjs/nest111 direct, 1484 transitive · 15 PRs waiting
A 98
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>.