GitHub

node-fetch

A light-weight module that brings Fetch API to node.js

npm says

275,599,564 / week

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

probably humans

≈ 275,564,391–275,599,564 / week

best guess 275,597,594 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 node-fetch?

npm counted 275,599,564 downloads of node-fetch 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 275,597,594 of them (likely range 275,564,391–275,599,564) were real human installs, with high confidence. That puts less than 1% of npm's weekly count down to robots.

Is node-fetch 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, 3.3.2, came out on Jul 25, 2023. There were no stable releases in the last 12 months. It was first published on Jan 27, 2015. npm lists 5 maintainers.

Is node-fetch still used?

Downloads with publish spikes removed are up 46% over 3 months and up 204% over 11 months. Last week, 59% of downloads above the crawler floor were on major version 2, not the latest one; the most used single version was 2.7.0, with 47%. Weekdays get 1.5× the downloads of weekends, which fits people at work, though CI follows the same rhythm. Crawlers account for about 2,016 downloads a week, roughly 21 per version.

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 an honest confidence level.

Read the methodology

Other packages