lodash.includes

The lodash method `_.includes` exported as a module.

npm says / week

npm says 77,666,669

real installs / week

≈ 77.6M–77.7M

high confidence

noise under 1% of npm's count, so filtering barely changes it.

Mirror spikes and crawlers removed. CI and dependency installs still count, so this is not a head count. Snapshot from the daily build of Nov 19, 2026, last 7 days of npm data. With JavaScript on, this page recomputes it live from the npm API.

How many people use lodash.includes?

npm counted 77,666,669 downloads of lodash.includes in the last 7 days. Nobody can count people exactly, npm included: it does not record who downloaded what. After removing mirror spikes and crawlers, about 77.6M–77.7M look like real installs. At this scale most of them come from CI, builds and other packages that depend on lodash.includes, so the number of people behind them is far smaller.

Is lodash.includes still maintained?

Probably not actively: there has been no release in over a year, though that can also mean it is simply finished. The latest version, 4.3.0, came out on Aug 13, 2016. There were no stable releases in the last 12 months. It was first published on Jan 26, 2015. npm lists 2 maintainers.

Is lodash.includes still used?

Downloads with publish spikes removed are up 57% over 3 months and up 235% over 11 months. For scale, the median of the 459 packages we track, which lean towards today's most downloaded, is up 169% over 11 months, so this one is ahead of that. Last week, 100% of downloads above the crawler floor were on major version 4, the latest one; the most used single version was 4.3.0, with 100%. Weekdays get 1.8× the downloads of weekends, which fits people at work, though CI follows the same rhythm. Crawlers account for about 185 downloads a week, roughly 14 per version.

Monthly downloads of lodash.includes

The busiest month was Oct 2026, with about 9,320,572 downloads a day once publish spikes are removed; the quietest was Dec 2025 (the holiday season), with about 2,834,328.

monthnpm downloadspublish spikes removedreal installsvs month before
Oct 2026 242,334,867 0 242M up 17%
Sep 2026 223,611,356 0 224M up 19%
Aug 2026 208,882,869 0 209M up 5%
Jul 2026 198,743,167 0 199M up 8%
Jun 2026 177,664,734 0 178M up 16%
May 2026 158,037,439 0 158M up 6%
Apr 2026 144,846,524 0 145M up 5%
Mar 2026 142,015,701 0 142M up 17%
Feb 2026 110,085,559 0 110M up 23%
Jan 2026 98,717,521 0 98.7M up 12%
Dec 2025 87,864,157 0 87.8M–87.9M —

Whole months through Oct 31, 2026. Publish spikes are found day by day and summed per month. Real installs apply this week's crawler share to each month's downloads (the upper end also keeps the removed spikes), so they follow npm's curve rather than measure it. The change compares spike-free downloads per day.

Where do the downloads of lodash.includes come from?

Probably mostly through other packages. Each package below requires the one above it, and their weekly downloads on the matching versions line up within about 30%. This is an inference from download counts, not something npm records.

  1. lodash.includes 4.3.0 77.7M a week
  2. jsonwebtoken 9.0.3 85.3M a week

Past jsonwebtoken the trail splits or we can't follow it. They still count as real installs, but the projects behind them may never have chosen lodash.includes directly. How a package ends up like this.

How the estimate works

  1. Cut the spike every new version gets from mirrors and scanners in its first days.
  2. Subtract the crawler floor: the flat count crawlers download from every version each week.
  3. Show what is left as a range, with a confidence level. It still includes CI and dependency installs, so it is not a count of people.

Read the methodology