@vitest/eslint-plugin
ESLint plugin for Vitest
npm says / week
npm says 6,068,562
real installs / week
≈ 6.04M–6.07M
noise under 1% of npm's count, so filtering barely changes it.
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 @vitest/eslint-plugin?
npm counted 6,068,562 downloads of @vitest/eslint-plugin 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 6.04M–6.07M look like real installs. At this scale most of them come from CI, builds and other packages that depend on @vitest/eslint-plugin, so the number of people behind them is far smaller.
Is @vitest/eslint-plugin still maintained?
Most likely yes, going by its releases. The latest version, 1.6.28, came out on Oct 22, 2026. The last 12 months saw 32 stable releases, typically 8 days apart. It was first published on Aug 10, 2024. npm lists 6 maintainers.
Is @vitest/eslint-plugin still used?
Downloads with publish spikes removed are up 56% over 3 months and up 166% 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 about level with that. Last week, 100% of downloads above the crawler floor were on major version 1, the latest one; the most used single version was 1.6.28, with 32%. Weekdays get 2.5× the downloads of weekends, which fits people at work, though CI follows the same rhythm. Crawlers account for about 5,441 downloads a week, roughly 45 per version.
Monthly downloads of @vitest/eslint-plugin
The busiest month was Oct 2026, with about 672,734 downloads a day once publish spikes are removed; the quietest was Dec 2025 (the holiday season), with about 260,409.
| month | npm downloads | publish spikes removed | real installs | vs month before |
|---|---|---|---|---|
| Oct 2026 | 17,491,074 | 0 | 17.4M–17.5M | up 14% |
| Sep 2026 | 17,117,662 | 0 | 17M–17.1M | up 17% |
| Aug 2026 | 15,585,167 | 0 | 15.5M–15.6M | about flat |
| Jul 2026 | 15,203,660 | 0 | 15.1M–15.2M | up 9% |
| Jun 2026 | 13,552,068 | 0 | 13.5M–13.6M | up 15% |
| May 2026 | 12,177,473 | 0 | 12.1M–12.2M | about flat |
| Apr 2026 | 11,536,069 | 0 | 11.5M | up 6% |
| Mar 2026 | 11,214,843 | 0 | 11.2M | up 12% |
| Feb 2026 | 9,077,061 | 0 | 9.04M–9.08M | up 12% |
| Jan 2026 | 8,964,137 | 0 | 8.93M–8.96M | up 11% |
| Dec 2025 | 8,072,673 | 0 | 8.04M–8.07M | — |
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.