balanced-match
Match balanced character pairs, like "{" and "}"
npm says
563,381,366
per week
Every tarball fetch: mirrors, scanners, CI and people.
real installs
high confidence≈ 563M
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: 1, not the latest one, with 53% of last week's downloads above the crawler floor. Most used single version: 1.0.2.
Snapshot from the daily build of Nov 9, 2026, last 7 days of npm data. With JavaScript on, this page recomputes it live from the npm API.
How many people use balanced-match?
npm counted 563,381,366 downloads of balanced-match 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 563M look like real installs. At this scale most of them come from CI, builds and other packages that depend on balanced-match, so the number of people behind them is far smaller.
Is balanced-match still maintained?
Most likely yes, going by its releases. The latest version, 5.0.0, came out on Oct 16, 2026. The last 12 months saw 4 stable releases, typically 9 days apart. It was first published on Oct 13, 2013. npm lists 1 maintainer.
Is balanced-match still used?
Downloads with publish spikes removed are up 44% over 3 months and up 478% 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 ahead of that. Last week, 53% of downloads above the crawler floor were on major version 1, not the latest one; the most used single version was 1.0.2, with 52%. Weekdays get 1.6× the downloads of weekends, which fits people at work, though CI follows the same rhythm. Crawlers account for about 3,291 downloads a week, roughly 173 per version.
Monthly downloads of balanced-match
The busiest month was Oct 2026, with about 72,163,873 downloads a day once publish spikes are removed; the quietest was Dec 2025 (the holiday season), with about 11,995,921.
| month | npm downloads | publish spikes removed | real installs | vs month before |
|---|---|---|---|---|
| Oct 2026 | 1,804,096,819 | 0 | 1.8B | up 13% |
| Sep 2026 | 1,722,985,167 | 0 | 1.72B | up 20% |
| Aug 2026 | 1,655,162,063 | 0 | 1.66B | about flat |
| Jul 2026 | 1,633,742,058 | 0 | 1.63B | up 7% |
| Jun 2026 | 1,482,334,288 | 0 | 1.48B | up 20% |
| May 2026 | 1,279,208,111 | 0 | 1.28B | up 15% |
| Apr 2026 | 1,080,601,295 | 0 | 1.08B | up 10% |
| Mar 2026 | 1,014,314,567 | 0 | 1.01B | up 56% |
| Feb 2026 | 586,524,579 | 0 | 586M–587M | up 32% |
| Jan 2026 | 491,873,514 | 0 | 492M | up 32% |
| Dec 2025 | 371,873,554 | 0 | 372M | — |
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.
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.