@everworker/oneringai
Unified TypeScript AI agent library with multi-vendor models, tools, memory, media, and pluggable OneRingAI/Codex agent…
npm says / week
npm says 1,711
real installs / week
≈ 1.29K–1.67K
About 20% of npm's count looks like noise.
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 19, 2026, last 7 days of npm data. With JavaScript on, this page recomputes it live from the npm API.
How many people use @everworker/oneringai?
npm counted 1,711 downloads of @everworker/oneringai 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 1.29K–1.67K look like real installs. Noise is 20% of npm's count. What remains still includes CI and installs as a dependency of other packages.
Is @everworker/oneringai still maintained?
Most likely yes, going by its releases. The latest version, 1.2.4, came out on Nov 17, 2026. The last 12 months saw 51 stable releases, typically 3 days apart. It was first published on Feb 5, 2026. npm lists 1 maintainer.
Is @everworker/oneringai still used?
Downloads with publish spikes removed are up 340% over 3 months. Last week, 98% of downloads above the crawler floor were on major version 1, the latest one; the most used single version was 1.2.2, with 37%. Weekdays get 0.58× the downloads of weekends, so there is no clear work-week rhythm. Over the last 12 months, 5,600 downloads arrived in publish spikes and were attributed to mirrors and scanners. Crawlers account for about 50 downloads a week, roughly 1 per version.
Monthly downloads of @everworker/oneringai
The busiest month was Oct 2026, with about 159 downloads a day once publish spikes are removed; the quietest was Apr 2026, with about 12.
| month | npm downloads | publish spikes removed | real installs | vs month before |
|---|---|---|---|---|
| Oct 2026 | 5,138 | 993 (19%) | 3.58K–5.01K | up 108% |
| Sep 2026 | 2,595 | 452 (17%) | 1.85K–2.53K | down 8% |
| Aug 2026 | 3,513 | 1,010 (29%) | 2.16K–3.44K | up 504% |
| Jul 2026 | 1,138 | 710 (62%) | 370–1.13K | up 7% |
| Jun 2026 | 350 | 0 | 302–339 | down 26% |
| May 2026 | 814 | 274 (34%) | 466–801 | up 47% |
| Apr 2026 | 1,024 | 668 (65%) | 304–1.01K | down 14% |
| Mar 2026 | 654 | 226 (35%) | 369–642 | — |
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.