npm download trends
npm Package Movers
See which tracked npm packages are gaining or losing download momentum using explainable 7-day comparisons. Missing registry days are excluded instead of silently counted as zero.
Reliable mover rankings are warming up
EcosystemPulse will not rank packages from broken or gapped npm download windows. The site needs 14 consecutive reliable calendar days before comparing one 7-day period with the previous 7.
Rising and falling rankings appear automatically when reliable evidence is complete and a change crosses the 5% threshold.
Current tracked npm activity
These are current registry observations, not momentum rankings.
| Package | Trailing-week downloads | Days since release | Version |
|---|---|---|---|
| zod | 442.97M | 20 | 4.6.7 |
| typescript | 401.22M | 116 | 7.0.2 |
| esbuild | 397.49M | 85 | 0.28.2 |
| node-fetch | 275.97M | 1166 | 3.3.2 |
| vite | 251.99M | 11 | 8.3.5 |
| react | 244.73M | 18 | 19.3.1 |
| lodash | 206.48M | 214 | 4.18.1 |
| eslint | 202.07M | 2 | 10.14.0 |
| express | 196.63M | 23 | 5.3.0 |
| prettier | 180.06M | 22 | 3.9.10 |
| vitest | 169.70M | 17 | 5.0.5 |
| tailwindcss | 167.73M | 108 | 4.3.3 |
| rollup | 161.30M | 0 | 4.67.4 |
| axios | 145.58M | 5 | 1.21.0 |
| date-fns | 118.60M | 156 | 4.4.0 |
How the ranking works
Momentum requires 14 consecutive reliable calendar days: the latest seven consecutive reliable npm download days are compared with the previous seven. EcosystemPulse detects coordinated zero-download anomalies across tracked packages, removes those dates, and waits for complete calendar windows before publishing a percentage.
Compare related packages → Browse all tracked npm packages →