@babel/parser
A JavaScript parser
npm says
354,500,044 / week
Every tarball fetch: mirrors, scanners, CI and people.
probably humans
≈ 351,396,675–354,498,224 / week
best guess 354,442,874 high confidence
Snapshot from the daily build of Nov 4, 2026, last 7 days of npm data. With JavaScript on, this page recomputes it live from the npm API.
How many people actually use @babel/parser?
npm counted 354,500,044 downloads of @babel/parser in the last 7 days. That count includes every tarball fetch: registry mirrors, security scanners, CI pipelines and crawlers as well as people. humanloads estimates that about 354,442,874 of them (likely range 351,396,675–354,498,224) were real human installs, with high confidence. That puts less than 1% of npm's weekly count down to robots.
Is @babel/parser still maintained?
Most likely yes, going by its releases. The latest version, 8.1.0, came out on Nov 2, 2026. The last 12 months saw 17 stable releases, typically 22 days apart, plus 7 pre-releases. It was first published on May 24, 2018. npm lists 4 maintainers.
Is @babel/parser still used?
Downloads with publish spikes removed are up 51% over 3 months and up 235% over 11 months. Last week, 92% of downloads above the crawler floor were on major version 7, not the latest one; the most used single version was 7.29.7, with 17%. Weekdays get 1.4× the downloads of weekends, which fits people at work, though CI follows the same rhythm. Crawlers account for about 61,412 downloads a week, roughly 236 per version.
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 an honest confidence level.