fill-range
Fill in a range of numbers or letters, optionally passing an increment or `step` to use, or create a regex-compatible r…
npm says
217,354,788
per week
Every tarball fetch: mirrors, scanners, CI and people.
real installs
high confidence≈ 217M
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.
Most used major version: 7, the latest one, with 91% of last week's downloads above the crawler floor. Most used single version: 7.1.1.
Snapshot from the daily build of Nov 6, 2026, last 7 days of npm data. With JavaScript on, this page recomputes it live from the npm API.
How many people use fill-range?
npm counted 217,354,788 downloads of fill-range 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 217M look like real installs. At this scale most of them come from CI, builds and other packages that depend on fill-range, so the number of people behind them is far smaller.
Is fill-range 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, 7.1.1, came out on May 21, 2024. There were no stable releases in the last 12 months. It was first published on Nov 25, 2014. npm lists 3 maintainers.
Is fill-range still used?
Downloads with publish spikes removed are up 26% over 3 months and up 107% over 11 months. For scale, the median of the 269 packages we track, which lean towards today's most downloaded, is up 157% over 11 months, so this one is behind that. Last week, 91% of downloads above the crawler floor were on major version 7, the latest one; the most used single version was 7.1.1, with 85%. Weekdays get 1.4× the downloads of weekends, which fits people at work, though CI follows the same rhythm. Crawlers account for about 568 downloads a week, roughly 17 per version.
Where do the downloads of fill-range 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.
- fill-range 7.1.1 217M a week
- braces 3.0.3 218M a week
Past braces the trail splits or we can't follow it. These are still real installs, but the people running them may never have chosen fill-range. How a package ends up like this.
How the estimate works
- Cut the spike every new version gets from mirrors in its first days.
- Subtract the flat floor robots download from every version each week.
- 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.