@webassemblyjs/wasm-parser
WebAssembly binary format parser
npm says / week
npm says 66,663,581
real installs / week
≈ 66.6M–66.7M
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 20, 2026, last 7 days of npm data. With JavaScript on, this page recomputes it live from the npm API.
How many people use @webassemblyjs/wasm-parser?
npm counted 66,663,581 downloads of @webassemblyjs/wasm-parser 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 66.6M–66.7M look like real installs. At this scale most of them come from CI, builds and other packages that depend on @webassemblyjs/wasm-parser, so the number of people behind them is far smaller.
Is @webassemblyjs/wasm-parser 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, 1.14.1, came out on Nov 6, 2024. There were no stable releases in the last 12 months. It was first published on Feb 25, 2018. npm lists 1 maintainer.
Is @webassemblyjs/wasm-parser still used?
Downloads with publish spikes removed are up 36% over 3 months and up 115% 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 behind that. Last week, 100% of downloads above the crawler floor were on major version 1, the latest one; the most used single version was 1.14.1, with 88%. Weekdays get 2.1× the downloads of weekends, which fits people at work, though CI follows the same rhythm. Crawlers account for about 1,424 downloads a week, roughly 16 per version.
Monthly downloads of @webassemblyjs/wasm-parser
The busiest month was Oct 2026, with about 8,300,628 downloads a day once publish spikes are removed; the quietest was Dec 2025 (the holiday season), with about 3,631,304.
| month | npm downloads | publish spikes removed | real installs | vs month before |
|---|---|---|---|---|
| Oct 2026 | 215,816,316 | 0 | 216M | up 7% |
| Sep 2026 | 225,395,127 | 0 | 225M | up 18% |
| Aug 2026 | 204,678,411 | 0 | 205M | about flat |
| Jul 2026 | 199,977,207 | 0 | 200M | up 6% |
| Jun 2026 | 182,289,838 | 0 | 182M | up 12% |
| May 2026 | 168,454,991 | 0 | 168M | about flat |
| Apr 2026 | 161,470,051 | 0 | 161M | about flat |
| Mar 2026 | 166,508,622 | 0 | 166M–167M | up 15% |
| Feb 2026 | 130,549,684 | 0 | 131M | up 22% |
| Jan 2026 | 118,952,848 | 0 | 119M | up 6% |
| Dec 2025 | 112,570,415 | 0 | 113M | — |
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 @webassemblyjs/wasm-parser 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.
- @webassemblyjs/wasm-parser 1.14.1 66.7M a week
- webpack 5.106.2 76.9M a week
Past webpack the trail splits or we can't follow it. They still count as real installs, but the projects behind them may never have chosen @webassemblyjs/wasm-parser directly. How a package ends up like this.
How the estimate works
- Cut the spike every new version gets from mirrors and scanners in its first days.
- Subtract the crawler floor: the flat count crawlers 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.