read-package-up
12.0.0 · 7 Nov 2025MIT12.7M / weekRepositoryHomepagenpmAtom feed
Where each line stands
Plan an upgrade- 12.x12.0.0No known advisoryLatest line
- 11.x11.0.0No known advisoryTo 12.0.0
What to use instead
A better maintained package
From the e18e module-replacements list, maintained by the community.
The list compares the options for read-package-up: read the comparison.
Before you switch
- 1
Check what else depends on it
Paste your package.json in the dependency check to see every deprecated or outdated package in one pass, not only this one.
- 2
Read the replacement's peers and releases
A native API or a few lines of code need no release notes, but check the Node version your project runs on.
- 3
Know when it ships
Follow the new package on inlinr: its releases and advisories land in your feed, and the time spent on the migration branch shows on its page.
Latest releases
Dependency tracking
Know when your own dependencies move
This page watches read-package-up. inlinr reads your package.json and keeps the same watch on every dependency you declare, then tells you only what needs you.
Advisories reach you
An email when a critical or high advisory affects a project, before the next install.
Upgrades checked first
Peer ranges, Node, ESM-only and types changes read before you bump.
Only what matters
Majors and breaking notes stay; patches and sibling bumps fold into one line.
Registry facts last checked 22 Nov 2026. Releases and advisories last read 22 Nov 2026.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.