NPM Download Stats API Bug Undermines Software Developer KPIs and Project Overviews

The Glitch in the Matrix: NPM Download Stats Report Zeros

A significant issue has emerged within the npm ecosystem, directly impacting how developers track package adoption and project success. The api.npmjs.org/downloads endpoint, a crucial source for package download statistics, has been consistently reporting zero downloads for numerous packages on specific days since July 2026. This isn't just a minor inconvenience; it directly distorts crucial software developer kpis and compromises the accuracy of any software project overview that relies on npm download metrics.

The problem, initially highlighted by ofri-peretz in a GitHub Community discussion, details a growing frequency of these 'zero days.' For example, nine of the first 24 days of October 2026 showed no downloads for even the most popular packages like react, typescript, and lodash. The surrounding days, however, show normal, high download volumes, indicating a data processing failure rather than a genuine drop in usage. This leads to weekly totals on npmjs.com being severely understated, often showing artificial drops of 70-85%.

The issue is easily reproducible using simple curl commands:

curl -s https://api.npmjs.org/downloads/range/2026-10-16:2026-10-24/react
curl -s https://api.npmjs.org/downloads/point/2026-10-20/react

The single-day point endpoint and per-version endpoints return the same erroneous zeros, leaving no public alternative for accurate data on these affected days. Here's an example of the reported daily downloads (in millions) for a selection of packages:

| Package    | Oct 18 | Oct 19 | Oct 20 | Oct 21 | Oct 22 | Oct 23 | Oct 24 |
|------------|--------|--------|--------|--------|--------|--------|--------|
| react      | 22.4   | 0      | 0      | 0      | 42.4   | 0      | 0      |
| typescript | 34.7   | 0      | 0      | 0      | 68.9   | 0      | 0      |
| semver     | 92.9   | 0      | 0      | 0      | 197.5  | 0      | 0      |

Why Reliable Data is Essential for Project Planning

For teams engaged in planning a software development project, accurate download statistics are vital. These metrics inform decisions, validate adoption, and measure the success of open-source contributions. When the API reports zeros, it creates a false narrative about package health and project trajectory. The community has confirmed this widespread issue, with users like tomwheeler reporting similar zeros for packages with millions of daily downloads, such as @temporalio/common, further emphasizing the systemic nature of the problem.

Community Calls for Action: Backfill, Clarity, and Transparency

The recurring nature of this issue — with similar incidents reported in September 2023 and February 2026 — underscores the need for a robust and transparent data pipeline. The community is advocating for several key improvements:

• Reprocess and backfill missing data: The primary request is to restore the correct download counts for all affected days. Previous successful data restorations demonstrate this is achievable.
• Improve API data representation: Instead of returning 0 for unprocessed days, the API should return null or a specific flag. This distinction is crucial for tools to differentiate between genuinely low activity and missing data, enhancing data integrity for software project overview dashboards.
• Enhance status page transparency: Add the downloads/stats pipeline status to status.npmjs.org. Currently, the page shows all green, despite significant data gaps, misleading developers about system health.

Reliable metrics are the bedrock of effective software developer kpi tracking and informed planning a software development project. Addressing these data integrity concerns is paramount for maintaining trust and utility in the npm ecosystem.