@dotcom-reliability-kit/logger
A simple and fast logger based on Pino, with FT preferences baked in
npm says / week
npm says 3,750
real installs / week
≈ 3.23K–3.48K
About 11% of npm's count looks like noise.
Most used major version: 2, not the latest one, with 45% of last week's downloads above the crawler floor. Most used single version: 2.4.2.
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 @dotcom-reliability-kit/logger?
npm counted 3,750 downloads of @dotcom-reliability-kit/logger 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 3.23K–3.48K look like real installs. Noise is 11% of npm's count. What remains still includes CI and installs as a dependency of other packages.
Is @dotcom-reliability-kit/logger still maintained?
Most likely yes, going by its releases. The latest version, 5.0.3, came out on Nov 11, 2026. The last 12 months saw 7 stable releases, typically 49 days apart, plus 1 pre-release. It was first published on Oct 25, 2022. npm lists 5 maintainers.
Is @dotcom-reliability-kit/logger still used?
Downloads with publish spikes removed are down 33% over 3 months and down 55% 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, 45% of downloads above the crawler floor were on major version 2, not the latest one; the most used single version was 2.4.2, with 37%. Weekdays get 3.9× the downloads of weekends, which fits people at work, though CI follows the same rhythm. Over the last 12 months, 1,481 downloads arrived in publish spikes and were attributed to mirrors and scanners. Crawlers account for about 313 downloads a week, roughly 5 per version.
Monthly downloads of @dotcom-reliability-kit/logger
The busiest month was Jul 2026, with about 1,444 downloads a day once publish spikes are removed; the quietest was Oct 2026, with about 589.
| month | npm downloads | publish spikes removed | real installs | vs month before |
|---|---|---|---|---|
| Oct 2026 | 15,319 | 0 | 13.2K–14.2K | down 22% |
| Sep 2026 | 21,098 | 0 | 18.2K–19.6K | up 13% |
| Aug 2026 | 20,703 | 0 | 17.8K–19.2K | down 54% |
| Jul 2026 | 44,755 | 0 | 38.5K–41.5K | about flat |
| Jun 2026 | 42,775 | 0 | 36.8K–39.7K | up 24% |
| May 2026 | 35,733 | 0 | 30.8K–33.1K | down 11% |
| Apr 2026 | 38,967 | 0 | 33.6K–36.1K | about flat |
| Mar 2026 | 41,532 | 0 | 35.8K–38.5K | about flat |
| Feb 2026 | 39,333 | 0 | 33.9K–36.5K | up 18% |
| Jan 2026 | 38,388 | 1,481 (4%) | 31.8K–35.7K | up 41% |
| Dec 2025 | 26,201 | 0 | 22.6K–24.3K | — |
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.