long
A Long class for representing a 64-bit two's-complement integer value.
npm says
128,056,407
per week
Every tarball fetch: mirrors, scanners, CI and people.
real installs
high confidence≈ 128M
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.
Most used major version: 5, the latest one, with 87% of last week's downloads above the crawler floor. Most used single version: 5.3.2.
Snapshot from the daily build of Nov 10, 2026, last 7 days of npm data. With JavaScript on, this page recomputes it live from the npm API.
How many people use long?
npm counted 128,056,407 downloads of long 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 128M look like real installs. At this scale most of them come from CI, builds and other packages that depend on long, so the number of people behind them is far smaller.
Is long 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, 5.3.2, came out on Apr 17, 2025. There were no stable releases in the last 12 months. It was first published on Mar 12, 2013. npm lists 1 maintainer.
Is long still used?
Downloads with publish spikes removed are up 52% over 3 months and up 231% 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 ahead of that. Last week, 87% of downloads above the crawler floor were on major version 5, the latest one; the most used single version was 5.3.2, with 79%. Weekdays get 1.7× the downloads of weekends, which fits people at work, though CI follows the same rhythm. Crawlers account for about 460 downloads a week, roughly 12 per version.
Monthly downloads of long
The busiest month was Oct 2026, with about 16,562,927 downloads a day once publish spikes are removed; the quietest was Dec 2025 (the holiday season), with about 4,941,068.
| month | npm downloads | publish spikes removed | real installs | vs month before |
|---|---|---|---|---|
| Oct 2026 | 430,636,108 | 0 | 431M | up 16% |
| Sep 2026 | 386,239,508 | 0 | 386M | up 20% |
| Aug 2026 | 370,535,382 | 0 | 370M–371M | up 8% |
| Jul 2026 | 341,990,448 | 0 | 342M | up 10% |
| Jun 2026 | 300,959,761 | 0 | 301M | up 13% |
| May 2026 | 275,689,583 | 0 | 276M | up 5% |
| Apr 2026 | 253,817,093 | 0 | 254M | about flat |
| Mar 2026 | 259,439,778 | 0 | 259M | up 20% |
| Feb 2026 | 195,568,958 | 0 | 196M | up 25% |
| Jan 2026 | 173,328,855 | 0 | 173M | up 13% |
| Dec 2025 | 153,173,123 | 0 | 153M | — |
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 long 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.
- long 5.3.2 128M a week
- protobufjs 7.6.6 123M a week
Past protobufjs the trail splits or we can't follow it. These are still real installs, but the people running them may never have chosen long. 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.