Issue Description:
I have observed that the download count for the ollama package on NPM remains at zero, which is very unexpected. It appears that this problem is not unique to this package but is affecting other packages as well due to an apparent bug with NPM’s tracking system. The issue might be causing misleading download statistics across the board. Can anyone explain why this anomaly is occurring, or provide insights into whether a resolution is in progress?
Any help or clarification from fellow developers would be greatly appreciated.
I encountered similar issues with my own package where the download numbers were misleading due to an apparent bug with npm’s tracking system. In my case, after a bit of investigation and following discussions on various forums, it turned out that npm was facing intermittent problems updating their download statistics, and this sometimes happened regardless of the package’s actual usage. I have been tracking discussions on their official channels and noticed that although a resolution has not yet been provided, many developers are aware of the problem and are awaiting further updates or fixes from npm.
hey i seen the same issue - npm seems to f up the download stats, it doesnt reflect the real numbers. just seems like a bug that needs sorting out
Based on my observations, the zero downloads count issue seems to be a recurring glitch with npm’s download statistics system rather than an anomaly specific to any one package. I have noticed similar discrepancies when tracking usage for other packages I work with, and it appears that npm’s tracking service is experiencing temporary hiccups. In my experience, developers have resorted to alternative metrics such as GitHub activity or user engagement to gauge package interest until npm resolves this bug. Continuing to monitor npm’s official channels and community feedback is advisable for updates on this issue.