npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@evlog/telemetry

v0.3.4

Published

Wide-event telemetry for CLIs and automation — evlog's one-event-per-run model for tools on user machines, with privacy-safe flags, consent, outbox, and auto disclosure

Readme

@evlog/telemetry

npm version npm downloads CI TypeScript Documentation license

Digging through logs is not observability. It's hope.

Wide-event telemetry for CLIs and automation, the same one-event-per-run model as evlog, built for tools that run on someone else's machine.

Ship usage insight without shipping an analytics SDK: wrap your citty command tree (or call createTelemetry() in scripts) and get one structured event per command: command name, sanitized flags, duration, outcome, and optional counters via telemetry.set().

Why evlog telemetry

| Problem | How this package solves it | | --- | --- | | Per-command analytics boilerplate | withTelemetry() walks your citty tree — one event per run handler | | Leaking paths, tokens, or raw argv | Privacy by shape: booleans/numbers captured, strings presence-only unless allowlisted | | Short-lived CI runs losing data | Disk-buffered NDJSON outbox drains on the next invocation | | Disclosure drift | generateDisclosure() derives markdown + JSON from your runtime config | | Ingestion endpoint | parseIngestBody() validates POST bodies server-side — tool allowlist, envelope checks, custom key filter | | Telemetry breaking the host tool | Never throws, never blocks exit; flush() hard-capped at 500ms |

Opt-out is first-class: DO_NOT_TRACK, EVLOG_TELEMETRY=0, or a persisted telemetry disable that purges undelivered data.

Size: ~28 KB ESM (~8.6 KB gzip) · server ingest subpath @evlog/telemetry/ingest ~5 KB · sideEffects: false · no evlog core dependency.

Install

pnpm add @evlog/telemetry

Quick start (citty)

import { defineCommand, runMain } from 'citty'
import { withTelemetry, defineTelemetryCommands, telemetry } from '@evlog/telemetry'

const TOOL = 'my-tool'
const VERSION = '1.0.0'

const main = withTelemetry(
  defineCommand({
    meta: { name: TOOL, version: VERSION },
    subCommands: {
      doctor: {
        meta: { name: 'doctor' },
        run() {
          telemetry.set({ checksFailed: 0 })
        },
      },
      telemetry: defineTelemetryCommands({ name: TOOL }),
    },
  }),
  { name: TOOL, version: VERSION },
)

runMain(main)

Scripts and GitHub Actions: createTelemetry() / createGitHubActionsTelemetry(). See the docs.

Docs

Full guide: evlog.dev telemetry guide

Example playground: examples/telemetry-playground in the evlog monorepo.