Lodash 4.18.1: A Maintenance Release in a Library That Refuses to Go Away
GitHub describes it as A modern JavaScript utility library delivering modularity, performance, & extras.. The repository metadata lists JavaScript as its primary language. The metadata lists the NOASSERTION license. This article stays within the project description and details documented in the GitHub repository README.
At a glance
- What is it?
- Lodash 4.18.1 is the latest release, published the day after 4.18.0, while the project transitions to a feature-complete stage. The library remains a pragmatic choice for teams that want battle-tested utilities without writing their own, but its age and governance shift deserve scrutiny.
- Who is it for?
- Adopt Lodash 4.18.1 if you need a stable, well-documented utility library with multiple build formats and a functional programming variant, especially in legacy or mixed environments. Do not adopt it if you prefer native ES2020+ methods and are willing to write a few helper functions.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository last received commits 45 days ago.
- What is it written in?
- Mainly JavaScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- lodash/lodash61,358 ★ · +36
| Repository | 2026-08-13 | 2026-11-15 |
|---|---|---|
| lodash/lodash | 61.3k | 61.4k |
36 Stars in the last 94 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What Lodash Actually Solves in 2026
The problem it solves has changed over time. Native JavaScript has caught up with many of Lodash's methods, such as `Object.assign`, `Array.from`, and `String.prototype.trim`. However, the library still offers utilities that have no direct native equivalent, like `_.debounce`, `_.throttle`, `_.cloneDeep`, and `_.get`. These are the reasons many projects still depend on it. The README does not claim to be better than native methods; it simply says it makes JavaScript easier. That is a modest claim, and it is accurate for the niche it fills.
How the Build System and Module Formats Work
The module formats go further. You can require the entire library, or you can cherry-pick individual methods like `require('lodash/at')` or `require('lodash/fp/curryN')`. This is intended to help bundlers like browserify, rollup, or webpack produce smaller output. There is also `lodash-es` for ES module consumers, plus plugins like `babel-plugin-lodash` and `lodash-webpack-plugin` that automatically trim unused methods. The README mentions these as part of the ecosystem, but it does not go into how to configure them. The README says the builds are generated with the `lodash-cli` tool. The command `lodash -o ./dist/lodash.js` produces a custom build, and `lodash core` produces the core version. This is a flexible system, but it also means you need to understand which build you are using and why.
Getting It Running: Installation and Basic Usage
The cherry-picking approach is important for anyone concerned about bundle size. However, the README does not explain the exact syntax for custom builds with lodash-cli beyond the basic commands. The README links the custom builds page at lodash.com/custom-builds for more. This is a minor gap, but it is worth noting if you plan to create a custom build.
The FP Build: A Different Paradigm, Not a Gimmick
The trade-off is that the FP build is not a drop-in replacement for the standard build. If you have existing code that uses the standard build, you cannot simply swap it. The argument order is reversed, and methods are curried, which means you need to refactor your code. The README describes the FP build as auto-curried, iteratee-first and data-last, which is what makes it not a drop-in replacement. For new projects, the FP build can be a clean start. For existing projects, it is a migration cost. That is a real limitation, and it is why you need to decide which build you want from the beginning.
Version 4.18.1: What Changed and Why It Matters
The significance is that Lodash is not dead. The OpenJS Foundation blog post mentioned in the README says the project received support from the Sovereign Tech Agency and will transition to a feature-complete maturity stage. That means no new features, but stability and security fixes. This is a deliberate choice. For adopters, it means you can expect the API to remain stable, but you should not expect new utilities. If you need a method that is not in Lodash, you will have to write it yourself or use another library. That is a concrete boundary. The governance reboot, with a new TSC, is meant to ensure the project remains sustainable. But it is also a change that could affect how quickly issues are resolved. You should verify that the new governance does not slow down security patches.
Limitations and When It Is the Wrong Tool
Another limitation is the FP build's learning curve. Auto-currying can be confusing for developers who are not familiar with functional programming. The README does not provide examples of how to debug FP code, so you are on your own. Also, the library does not handle asynchronous operations. There is no `_.async` or `_.promise` category. For that, you need to combine Lodash with `Promise.all` or a library like Bluebird. This is not a criticism; it is just a boundary. But you should know that Lodash does not solve concurrency or async flow control.
Alternatives: Native Methods and Ramda
A more direct alternative in the functional programming space is Ramda. Ramda also provides auto-curried, iteratee-first, data-last methods. But Ramda is designed from the ground up for functional composition, and it has a cleaner API for that purpose. Lodash's FP build is an add-on, not the primary design. If you are building a functional codebase, Ramda might be a better fit. However, Ramda does not have the same breadth of utilities as Lodash; for example, it lacks a `_.debounce` equivalent. So the choice depends on whether you need a general-purpose utility library or a dedicated functional toolkit.
Maintenance, Governance, and License Implications
The license is listed as MIT, which is permissive. The README confirms it. This means you can use Lodash in commercial projects, modify it, and distribute it, as long as you include the copyright notice. There are no copyleft obligations. This is a low-risk license for most organizations. However, the repository metadata says 'NOASSERTION' for the license field, which is odd. The README clearly states MIT, but the GitHub API does not recognize it. This could be a metadata issue, but you should verify the LICENSE file in the repository before relying on it. The README links to the LICENSE file, so that is a good place to check. For legal advice, consult a lawyer, but MIT is generally safe for internal and commercial use.
Editorial conclusion
Adopt Lodash 4.18.1 if you need a stable, well-documented utility library with multiple build formats and a functional programming variant, especially in legacy or mixed environments. Do not adopt it if you prefer native ES2020+ methods and are willing to write a few helper functions. Before upgrading from 4.17.x, verify your project's dependency tree for any tooling that assumes a specific Lodash build, and test the FP module if you rely on auto-curried methods. Also, check the upcoming TSC charter and governance changes, as they will determine whether the project remains as reliable as it has been.
Frequently asked questions
What is Lodash used for?
Lodash takes over the repetitive parts of working with arrays, numbers, objects and strings: iterating them, manipulating and testing values, and building composite functions. Its methods are modular, so you can take the whole library or single methods.
Is Lodash still relevant?
The documentation says Lodash has support from the Sovereign Tech Agency and will move to the Feature-Complete maturity stage, which means stable and secure rather than feature heavy. The last push to the repository was on 2026-10-01 and the current release is 4.18.1.
What can I use to replace Lodash?
The documentation names no alternative library. What it does offer is a smaller surface of the same library: the core build at about 4 kB gzipped against 24 kB for the full build, per method packages under the npm keyword lodash-modularized, and custom builds.
Is Lodash available on NPM?
Yes. The installation section uses npm i --save lodash, and the module formats list adds lodash-es, lodash-amd, the lodash/fp variant and per method packages published under the lodash-modularized keyword.
How do I install Lodash?
In a browser, load it with a script tag pointing at lodash.js. With npm, run npm i --save lodash, then require the full build with lodash, the core build with lodash/core, the fp build with lodash/fp, or a single method such as lodash/at.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/lodash-lodash)Star history chart for your README
[](https://hysenlabs.com/projects/lodash-lodash)Was this useful?