ms
Tiny millisecond conversion utility
npm says
727,491,564
per week
Every tarball fetch: mirrors, scanners, CI and people.
real installs
high confidence≈ 727M
per week
Mirror spikes and crawlers removed. CI and dependency installs still count, so this is not a head count.
noise under 1% of npm's count, so nearly all of it counts. noise real installs
Why this estimate
With JavaScript on, this lists what the filter found for this package.
Snapshot from the daily build of Nov 9, 2026, last 7 days of npm data. With JavaScript on, this page recomputes it live from the npm API.
How many people use ms?
npm counted 727,491,564 downloads of ms in the last 7 days. Nobody can count people exactly, npm included: it does not record who downloaded what. After removing mirror spikes and crawlers, about 727M look like real installs. At this scale most of them come from CI, builds and other packages that depend on ms, so the number of people behind them is far smaller.
Is ms 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, 2.1.3, came out on Dec 8, 2020. There were no stable releases in the last 12 months. It was first published on Dec 21, 2011. npm lists 6 maintainers.
Is ms still used?
Downloads with publish spikes removed are up 33% over 3 months and up 121% over 11 months. For scale, the median of the 384 packages we track, which lean towards today's most downloaded, is up 164% over 11 months, so this one is behind that. Last week, 100% of downloads above the crawler floor were on major version 2, the latest one; the most used single version was 2.1.3, with 57%. Weekdays get 1.5× the downloads of weekends, which fits people at work, though CI follows the same rhythm. Crawlers account for about 2,581 downloads a week, roughly 78 per version.
Monthly downloads of ms
The busiest month was Oct 2026, with about 94,757,093 downloads a day once publish spikes are removed; the quietest was Dec 2025 (the holiday season), with about 39,589,099.
| month | npm downloads | publish spikes removed | real installs | vs month before |
|---|---|---|---|---|
| Oct 2026 | 2,368,927,333 | 0 | 2.37B | up 8% |
| Sep 2026 | 2,378,729,121 | 0 | 2.38B | up 18% |
| Aug 2026 | 2,313,036,001 | 0 | 2.31B | about flat |
| Jul 2026 | 2,267,668,181 | 0 | 2.27B | about flat |
| Jun 2026 | 2,114,744,265 | 0 | 2.11B | up 11% |
| May 2026 | 1,962,513,399 | 0 | 1.96B | up 6% |
| Apr 2026 | 1,792,506,730 | 0 | 1.79B | about flat |
| Mar 2026 | 1,878,025,532 | 0 | 1.88B | up 18% |
| Feb 2026 | 1,433,453,517 | 0 | 1.43B | up 16% |
| Jan 2026 | 1,370,821,833 | 0 | 1.37B | up 12% |
| Dec 2025 | 1,227,262,062 | 0 | 1.23B | — |
Whole months through Oct 31, 2026. Publish spikes are found day by day and summed per month. Real installs apply this week's crawler share to each month's downloads (the upper end also keeps the removed spikes), so they follow npm's curve rather than measure it. The change compares spike-free downloads per day.
Where do the downloads of ms come from?
Probably mostly through other packages. Each package below requires the one above it, and their weekly downloads on the matching versions line up within about 30%. This is an inference from download counts, not something npm records.
Past debug the trail splits or we can't follow it. These are still real installs, but the people running them may never have chosen ms. How a package ends up like this.
How the estimate works
- Cut the spike every new version gets from mirrors in its first days.
- Subtract the flat floor robots download from every version each week.
- Show what is left as a range, with a confidence level. It still includes CI and dependency installs, so it is not a count of people.