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

@reviseflow/pulse-otel

v0.2.2

Published

Optional content-free MCP handler spans for OpenTelemetry. / OpenTelemetry için isteğe bağlı, içeriksiz MCP handler span’leri.

Readme

@reviseflow/pulse-otel

An optional MIT-licensed exporter that sends Pulse handler observations to your OpenTelemetry tracer. Core and the MCP adapter do not import this package.

Version 0.2.2 · MIT · Node.js 24 ESM. The API requires an explicit exporter. Migrate from 0.1.0 before upgrading an existing integration.

TR: 0.2.2 · MIT · Node.js 24 ESM. API açık bir exporter gerektirir; mevcut 0.1.0 kurulumu için önce geçiş rehberini okuyun.

Install / Kurulum

npm install --save-exact @reviseflow/[email protected] @reviseflow/[email protected] @opentelemetry/[email protected]

0.2.2 aligns with Pulse Core 0.2.2; OTel mapping and tracer ownership are unchanged. No migration is needed from 0.2.0.

Pass your configured tracer to the exporter, then inject it into Pulse:

import type { Tracer } from '@opentelemetry/api';
import { createPulseCore } from '@reviseflow/pulse-core';
import { createOtelExporter } from '@reviseflow/pulse-otel';

export function pulseForTracer(tracer: Tracer) {
  return createPulseCore({
    environment: 'production',
    exporter: createOtelExporter({ tracer }),
  });
}

The same exporter can be passed to the MCP adapter's createPulse. A full example with a real MCP client/server and an in-memory OTel provider is in examples/otel.ts. Run pnpm example:otel from the SDK checkout.

Semantics and limits

  • Emits one INTERNAL pulse.tool_handler span per event with allowlisted metadata. Handler duration is not full MCP request latency.
  • Does not copy identities, arguments, results, exceptions or prompts. Sampling and coverage remain unknown.
  • Acceptance means local tracer handoff, not remote receipt. Your application owns provider configuration, flush and shutdown; Pulse does not mutate the global provider.
  • Replay protection keeps 1,000 recent IDs by default. Same ID/body returns duplicate; a changed body returns EVENT_ID_CONFLICT. A failed tracer handoff does not become success on replay.
  • Cache entries contain fixed-size SHA-256 fingerprints produced by Node's crypto API, not serialized event bodies. There is no durable or exactly-once guarantee.
  • Wire timestamps JavaScript cannot represent, including leap seconds, return INVALID_EVENT. Explicit epoch tuples preserve representable historical times; the original numeric handler duration remains an attribute. No current-time fallback is created.

This is a Node.js integration. Reverse ingestion from existing spans is not implemented. See the OTel mapping and scope and privacy guide.

Türkçe

0.2.2, Pulse Core 0.2.2 ile hizalanır; OTel eşlemesi ve tracer sorumluluğu değişmez. 0.2.0’dan geçişte migration gerekmez.

Kendi OTel tracer'ınızı verin ve exporter'ı createPulseCore veya MCP adaptörünün createPulse fonksiyonuna aktarın. Yukarıdaki npm komutuyla tam sürümleri kurun. Tam gerçek MCP örneği için depoda pnpm example:otel çalıştırın.

Yalnızca izinli handler metadata'sı INTERNAL span olarak aktarılır. Handler süresi tam MCP gecikmesi değildir. Kimlik, argüman, sonuç, hata veya prompt kopyalanmaz. Örnekleme kapsamı bilinmiyor olarak kalır. Kabul, yerel tracer'a teslimdir; uzak teslim ve provider yaşam döngüsü uygulamanın sorumluluğudur.

Tekrar önbelleği varsayılan olarak son 1.000 ID ile sınırlıdır. Aynı ID/gövde tekrar sayılır; farklı gövde EVENT_ID_CONFLICT döndürür. Başarısız teslimin tekrarı başarılı alındı sayılmaz. Olay gövdeleri yerine Node kripto API'siyle sabit boyutlu SHA-256 parmak izleri tutulur.

JavaScript'in temsil edemediği zamanlar, artık saniye dahil, INVALID_EVENT döndürür; güncel saatle yedek veri üretilmez. Bu paket Node.js içindir, mevcut span'lardan ters veri alımı uygulanmamıştır. Kalıcı veya exactly-once teslim garantisi yoktur.

Practical guides / Uygulamalı rehberler

English guides · Türkçe rehberler · Local SDK source / Yerel SDK kaynağı

The MIT SDK works independently of the proprietary Cloud service. Explore the labelled Cloud demo when shared views and managed retention become useful; package installation does not create a subscription.

MIT SDK, kapalı kaynak Cloud servisinden bağımsızdır. Ortak görünümler ve yönetilen saklama gerektiğinde etiketlenmiş Cloud demosunu inceleyin; paket kurulumu abonelik oluşturmaz.