npm download statistics return zero on October 6 and 13–15, 2026 — backfill request

[ragojose]

🏷️ Discussion Type

Bug

Body

The npm downloads API reports zero for xmcp, react, typescript, and express on 2026-10-06, 2026-10-13, 2026-10-14, and 2026-10-15. I rechecked these dates on October 21, 2026. Surrounding days have nonzero counts, suggesting missing statistics across packages rather than an actual drop to zero.

Observed daily counts (UTC)

Date	xmcp	react	typescript	express
2026-10-05	3711	35446968	58791501	27252855
2026-10-06	0	0	0	0
2026-10-07	3205	35968597	61259910	30256724
2026-10-12	3214	34927798	57160641	27464781
2026-10-13	0	0	0	0
2026-10-14	0	0	0	0
2026-10-15	0	0	0	0
2026-10-16	1812	36331234	58943628	29398494

Reproduction

Public endpoints, no authentication required:

curl -fsSL https://api.npmjs.org/downloads/range/2026-10-05:2026-10-16/xmcp
curl -fsSL https://api.npmjs.org/downloads/range/2026-10-05:2026-10-16/react
curl -fsSL https://api.npmjs.org/downloads/range/2026-10-05:2026-10-16/typescript
curl -fsSL https://api.npmjs.org/downloads/range/2026-10-05:2026-10-16/express

Impact and requested action

Download charts and totals covering these dates appear incomplete. The zero days are visible for xmcp at https://npm-stat.com/charts.html?package=xmcp and https://www.npmjs.com/package/xmcp.

1. Please investigate and reprocess/backfill the affected dates where source logs are available.
2. Can the counts be recovered, and is there an expected timeline?
3. Could the API expose an unavailable/incomplete marker for unprocessed dates so consumers can distinguish missing statistics from genuine zero downloads?

Related report: https://github.com/orgs/community/discussions/210819 — closed by automation for submission-format reasons, not marked resolved. This report uses the npm discussion template and adds independently verified xmcp data.

This concerns download statistics; it does not establish a package installation outage. No replacement counts have been estimated.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[zuchka]

can confirm this issue w these packages and others too

[bytesbydev]

I’d suggest adding an explicit data_status field to the downloads API, with values like complete, incomplete, or unavailable. This would help developers distinguish genuine zero downloads from missing statistics and avoid inaccurate charts or reports. The npm team could also consider backfilling the affected dates if the original data is recoverable.

[codehippie1]

Is the npm team tagged on this issue to fix the backfill?