lodash
4.18.1 · 1 Apr 2026MIT136.3M / weekRepositoryHomepagenpmAtom feed
Where each line stands
Plan an upgrade- 4.x4.18.1Safe from 4.18.0Latest line
- 3.x and older3.10.166 open advisories, worst critical · last release Aug 2015, no longer updatedTo 4.18.1
What to use instead
A better maintained package
From the e18e module-replacements list, maintained by the community.
The list compares the options for lodash: 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
All 113 releasesNotes older than 90 days are read on the Releases tab.
Dependency tracking · free for 3 projects
Know when your own dependencies move
lodash had 3 security advisories in the last 12 months. Inlinr emails you the day one touches a project of yours, with the version that fixes it.
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 28 Oct 2026. Releases and advisories last read 28 Oct 2026.