@smithy/eventstream-codec
npm says / week
npm says 34,358,372
real installs / week
≈ 32.9M–34.4M
About 1% of npm's count looks like noise.
Most used major version: 4, the latest one, with 74% of last week's downloads above the crawler floor. Most used single version: 4.2.14.
Mirror spikes and crawlers removed. CI and dependency installs still count, so this is not a head count. Snapshot from the daily build of Nov 20, 2026, last 7 days of npm data. With JavaScript on, this page recomputes it live from the npm API.
How many people use @smithy/eventstream-codec?
npm counted 34,358,372 downloads of @smithy/eventstream-codec 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 32.9M–34.4M look like real installs. Noise is 1% of npm's count. What remains still includes CI and installs as a dependency of other packages.
Is @smithy/eventstream-codec still maintained?
Most likely yes, going by its releases. The latest version, 4.5.2, came out on Aug 15, 2026. The last 12 months saw 37 stable releases, typically 4 days apart. It was first published on Jun 19, 2023. npm lists 2 maintainers.
Is @smithy/eventstream-codec still used?
Downloads with publish spikes removed are up 28% over 3 months and up 83% over 11 months. For scale, the median of the 459 packages we track, which lean towards today's most downloaded, is up 169% over 11 months, so this one is behind that. Last week, 74% of downloads above the crawler floor were on major version 4, the latest one; the most used single version was 4.2.14, with 18%. Weekdays get 2.2× the downloads of weekends, which fits people at work, though CI follows the same rhythm. Crawlers account for about 425,528 downloads a week, roughly 4,625 per version.
Monthly downloads of @smithy/eventstream-codec
The busiest month was Apr 2026, with about 4,367,950 downloads a day once publish spikes are removed; the quietest was Dec 2025 (the holiday season), with about 2,297,280.
| month | npm downloads | publish spikes removed | real installs | vs month before |
|---|---|---|---|---|
| Oct 2026 | 109,162,445 | 0 | 105M–109M | up 9% |
| Sep 2026 | 111,803,183 | 0 | 107M–112M | up 8% |
| Aug 2026 | 110,577,404 | 0 | 106M–111M | about flat |
| Jul 2026 | 109,583,927 | 0 | 105M–110M | about flat |
| Jun 2026 | 107,215,997 | 0 | 103M–107M | down 9% |
| May 2026 | 122,002,423 | 0 | 117M–122M | down 10% |
| Apr 2026 | 131,038,508 | 0 | 126M–131M | up 8% |
| Mar 2026 | 125,274,011 | 0 | 120M–125M | up 22% |
| Feb 2026 | 92,895,800 | 0 | 89M–92.9M | up 24% |
| Jan 2026 | 83,268,849 | 0 | 79.8M–83.3M | up 17% |
| Dec 2025 | 71,215,695 | 0 | 68.2M–71.2M | — |
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.
How the estimate works
- Cut the spike every new version gets from mirrors and scanners in its first days.
- Subtract the crawler floor: the flat count crawlers 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.