GitHub

@humanwhocodes/config-array

Glob-based configuration matching.

Deprecated on npm. The maintainers' message: “Use @eslint/config-array instead”

npm says

40,064,369

per week

Every tarball fetch: mirrors, scanners, CI and people.

real installs

high confidence

≈ 40.1M

per week

Mirror spikes and crawlers removed. CI and dependency installs still count, so this is not a head count.

noise under 1% of npm's count, so nearly all of it counts. noise real installs

Why this estimate

With JavaScript on, this lists what the filter found for this package.

Snapshot from the daily build of Nov 10, 2026, last 7 days of npm data. With JavaScript on, this page recomputes it live from the npm API.

How many people use @humanwhocodes/config-array?

npm counted 40,064,369 downloads of @humanwhocodes/config-array 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 40.1M look like real installs. At this scale most of them come from CI, builds and other packages that depend on @humanwhocodes/config-array, so the number of people behind them is far smaller.

Is @humanwhocodes/config-array still maintained?

No: the latest version is marked deprecated on npm, with the message “Use @eslint/config-array instead”. The latest version, 0.13.0, came out on Apr 17, 2024. There were no stable releases in the last 12 months. It was first published on Nov 25, 2019. npm lists 1 maintainer.

Is @humanwhocodes/config-array still used?

Downloads with publish spikes removed are up 9% over 3 months and up 26% over 11 months. For scale, the median of the 384 packages we track, which lean towards today's most downloaded, is up 164% over 11 months, so this one is behind that. Last week, 100% of downloads above the crawler floor were on major version 0, the latest one; the most used single version was 0.13.0, with 61%. Weekdays get 2.0× the downloads of weekends, which fits people at work, though CI follows the same rhythm. Crawlers account for about 220 downloads a week, roughly 5 per version.

Monthly downloads of @humanwhocodes/config-array

The busiest month was Sep 2026, with about 5,728,320 downloads a day once publish spikes are removed; the quietest was Dec 2025 (the holiday season), with about 3,879,127.

monthnpm downloadspublish spikes removedreal installsvs month before
Oct 2026 144,791,287 0 145M about flat
Sep 2026 154,664,638 0 155M up 12%
Aug 2026 157,930,373 0 158M about flat
Jul 2026 159,441,657 0 159M about flat
Jun 2026 152,419,577 0 152M up 7%
May 2026 146,787,014 0 147M about flat
Apr 2026 145,130,040 0 145M about flat
Mar 2026 155,005,474 0 155M about flat
Feb 2026 133,676,742 0 134M up 18%
Jan 2026 125,534,644 0 125M–126M about flat
Dec 2025 120,252,929 0 120M —

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 @humanwhocodes/config-array 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. @humanwhocodes/config-array 0.13.0 40.1M a week
  2. eslint 9.39.5 204M a week

Past eslint the trail splits or we can't follow it. These are still real installs, but the people running them may never have chosen @humanwhocodes/config-array. How a package ends up like this.

How the estimate works

  1. Cut the spike every new version gets from mirrors in its first days.
  2. Subtract the flat floor robots 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

Other packages