Download websites that use Lodash

About Lodash

Every count of a client side JavaScript libraries is really a count of the copies that survived the build step, and nowhere is that gap wider than here. Lodash is designed to be consumed a function at a time, imported into a bundle and shaken free of everything the application never calls. A project that does exactly what the documentation recommends will ship code from this library while leaving no recognisable trace of it in the delivered page. So the honest framing is this. What we detect is the visible layer, meaning a standalone script served from a public path or a content delivery network, or a bundle that kept enough identifying structure to be recognised. The invisible layer is larger, and no crawler recovers it.

With that stated plainly, the visible layer is still worth having, because it is not a random sample. As of October 2026 we record the library on 3,803,855 sites. A separately loaded utility script generally means one of a few things, a page assembled without a modern bundler, a theme or plugin that carries its own dependencies, an older application that has been maintained rather than rebuilt, or a page where a tag manager or vendor widget pulled the library in on its own account. Each of those is a meaningful signal about how the site is built and who is likely to be maintaining it.

The library's history explains why so much of the web reaches for it. Released in 2012 under the MIT licence, it filled a gap in the language itself, offering dependable helpers for arrays, objects, collections and functional composition at a time when the standard library offered very little of that. Availability without cost or negotiation is the reason it spread into commercial products, agency templates and vendor scripts alike. Much of what it does has since arrived in the language, which makes a fresh dependency less necessary today and makes existing usage a reasonable proxy for code that predates the change or has simply not been revisited.

That proxy is the practical value. Security and compliance teams want an inventory of pages loading a general purpose utility script from a path they do not control. Anyone selling modernisation, performance work or framework migration wants the sites still assembling pages the older way. Researchers tracking how quickly the web replaces its dependencies want a longitudinal population rather than a handful of examples. The geography behaves the way developer tooling usually does, with United States accounting for 3,453,622 of the total and .com the suffix we record most often, which reflects where commercial web development is concentrated more than any preference in the library itself.

None of these questions can be answered one domain at a time. A lookup confirms a suspicion you already had about a site you already named. The exported list starts from the technology and hands back the population, joined to hosting, country, suffix and the rest of the detected stack, so you can slice it into the segment that matters to you. Read alongside the caveat above, meaning a floor rather than a census, the file supports comparisons across markets and across time that no single site check can produce.