Is lodash healthy, maintained, and safe?
No — lodash carries 1 unpatched critical advisory and should not be adopted without a remediation plan.
The verdict
lodash earns a health score of 35/100, a high risk rating, computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. No — lodash carries 1 unpatched critical advisory and should not be adopted without a remediation plan.
The last release was 1 April 2026 (118 days ago); still within a normal window, but the cadence has quietened. Across 117 releases the cadence has been steady, which is a good sign of an ongoing maintenance rhythm. Ownership rests on a single maintainer — a bus-factor of one, meaning one person's availability is a single point of failure for everyone downstream.
OSV lists 10 known advisories for lodash, including 1 critical and 4 high. Open critical advisories are the strongest possible signal to pin to a patched version, replace, or fork before shipping. Each advisory is listed with its OSV/GHSA identifier below.
Treat lodash as a liability to manage: review the evidence above, pin or patch, and evaluate alternatives. This is a one-time snapshot of a single package — real projects depend on dozens or hundreds of packages, and any one of them can drift or be compromised between releases. Run your own package.json through the free health check, or have OSPulse monitor your whole dependency tree continuously.
Evidence trail — deterministic, auditable
Known vulnerabilities (10)
Regular Expression Denial of Service (ReDoS) in lodash
Command Injection in lodash
Prototype Pollution in lodash
lodash vulnerable to Prototype Pollution via array path bypass in `_.unset` and `_.omit`
Prototype Pollution in lodash
Prototype Pollution in lodash
Prototype Pollution in lodash
lodash vulnerable to Code Injection via `_.template` imports key names
Regular Expression Denial of Service (ReDoS) in lodash
Lodash has Prototype Pollution Vulnerability in `_.unset` and `_.omit` functions
Key facts
- Latest version
- v4.18.1
- Last release
- 1 April 2026 (118 days ago)
- Total releases
- 117
- First release
- 23 April 2012
- Package age
- 14.3 years
- Maintainers
- 1
- Known advisories
- 10
- Confidence
- High
Frequently asked
Is lodash still maintained?
Partly — the most recent release was 1 April 2026 (118 days ago), so maintenance has slowed but not fully stopped.
Does lodash have known security vulnerabilities?
Yes — OSV lists 10 advisories for lodash, including 1 rated critical. See the advisory list on this page for the OSV/GHSA identifiers.
Is lodash safe to use?
No — lodash carries 1 unpatched critical advisory and should not be adopted without a remediation plan. OSPulse rates it 35/100 (high risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Other npm packages we've checked
lodash is one package. What about the other hundreds in your tree?
Paste your own package.json into the free health check for an instant snapshot — or let OSPulse monitor your whole dependency tree continuously, before your CVE scanner wakes up.
Data from the npm registry & OSV.dev · snapshot generated 2026-07-28 · scores are deterministic and recomputed on each refresh.