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

@pome-sh/wire

v0.4.3

Published

Pome's wire format — Zod schemas for recorder events, the OpenTelemetry extension surface, secret redaction, and framework-agnostic trace correlation. Shared by every twin, the sdk, the adapter and the CLI.

Readme

@pome-sh/wire

@pome-sh/wire defines trace data shared across Pome processes. It contains Zod schemas, TypeScript types, secret redaction, OpenTelemetry mappings, and tool-call correlation.

This package is published only to GitHub Packages at npm.pkg.github.com. It is not published to npm.

The CLI bundles this package. End users do not install it or need GitHub Packages credentials. Other Pome repositories use the published package.

zod is a peer dependency.

Scope

The package contains:

  • recorder event schemas, including TwinHttpEvent
  • secret redaction
  • OpenTelemetry event schemas and mappings
  • tool-call correlation helpers
  • run-completeness helpers
  • trace-contract.json, which describes the recorder event kinds

Sessions, tasks, runs, API error envelopes, and the pome.json schema are not part of the trace format. Those definitions remain in cli/src/contract/.

Use

import { recorderEventSchema, redactSecrets } from "@pome-sh/wire";
import { eventSchema } from "@pome-sh/wire/recorder-events";

const event = recorderEventSchema.parse(row);
const safe = redactSecrets(JSON.stringify(event));

Available subpaths are:

  • ./recorder-events
  • ./otel
  • ./otel/fixtures
  • ./redaction
  • ./correlation
  • ./run-completeness

Correlation

@pome-sh/wire/correlation associates an outbound request with the agent tool call that caused it.

The module stores the tool-call ID in AsyncLocalStorage. Its fetch hook adds x-pome-correlation-id only to configured twin origins.

import {
  generateToolCallId,
  installCorrelationFetchHook,
  withCorrelation,
} from "@pome-sh/wire/correlation";

installCorrelationFetchHook({ twinHosts: ["http://127.0.0.1:3333"] });

const id = readFrameworkToolCallId(call) ?? generateToolCallId();
return withCorrelation(id, () => handler(args));

An adapter supplies readFrameworkToolCallId. The correlation module does not depend on an agent framework.

This subpath is not on the root barrel because importing it creates an AsyncLocalStorage instance. The import does not patch fetch. Only installCorrelationFetchHook() patches fetch.

Run completeness

@pome-sh/wire/run-completeness exports shared values and predicates for criterion results:

  • PRE_SATISFIED_REASON
  • ADVISORY_SCORE_STATE
  • ABSTAINED_SCORE_STATE
  • tallyCriteriaResults
  • isIncompleteTally

This subpath is not on the root barrel because twins do not evaluate completed runs.

Trace contract

trace-contract.json lists each recorder event kind and its fixture.

Run this check after a recorder schema change:

npm run check:trace-contract -w @pome-sh/wire

License: Apache-2.0.