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

@compose-market/core

v0.2.21

Published

Shared Compose.Market SDK runtime primitives: HTTP client, typed errors, retries, storage, streaming parsers, receipts, and x402 wire types.

Readme

@compose-market/core

Shared runtime primitives for Compose.Market SDKs.

This package contains the reusable, product-agnostic pieces used by higher-level Compose clients:

  • typed Compose error classes
  • a dependency-free Fetch-based HTTP client with retries and timeouts
  • x402 PaymentRequired parsing
  • session-budget and receipt helpers
  • SSE parsing
  • minimal pluggable storage helpers
  • the single client-side decoder for the Compose agent/model domain event streams

Generated Speakeasy SDK output should remain generated. Higher-level SDKs can depend on this package as normal npm code without self-imports or generated-file patches.

Domain event stream contract

Both servers (the api gateway and the runtime) stream agent activity as a single typed event protocol. sse/stream parses the SSE transport and routes each frame to one of two decoders:

  • activity.decodeActivityEvent: { domain: "activity", type: "activity.*", id, ts, kind, status?, runId?, rootId?, parentId?, spanId?, target?, name?, delta?, payload? }
  • model.decodeModelEvent: { domain: "model", type: "model.*", id, ts, ... }

Event types:

  • activity.run (terminal carries payload.usage once, plus payload.agent and optional payload.memory/payload.reason), activity.thinking, activity.tool (payload { toolCallId, input, output, message, error }), activity.selection, activity.plan, activity.connector, activity.child (tree via parentId/path), activity.conclave, activity.message, activity.error
  • model.start, model.text.delta/model.text.done, model.reasoning.delta/model.reasoning.done, model.tool.delta/model.tool.done, model.asset (typed ModelAsset, never raw), model.status, model.done, model.error

target is an EventDisplay { kind?, id, name, target?, summary?, details? } — the server-owned, human-readable projection. Clients render from target, not from internal protocol fields.

The legacy runtime wire names (tool_start, swarm_child_*, plan.proposed, connector.connection_*, trace, timing, artifact.created, and friends) were removed with the runtime's hard cutover to domain events. The inference Responses wire (response.*, chat choices, text-delta, provider event names) is still decoded for /v1/responses streams.

Separation of concerns

  • Servers (api, runtime) import nothing from packages/.
  • core is the only client-side decoder; the SDK, web, and the Rust crates consume its contract. Rust parity is enforced by literal duplicated-frame tests in packages/sdk/rust/sdk/tests/parity.rs.
  • raw payload fields are durable/server-side only and never appear on user-visible streams.