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

@soa-harness/runner

v1.3.3

Published

SOA-Harness Runner — HTTP surface, trust bootstrap, Agent Card, StreamEvents, permission resolver, attestation, audit, probes. §19.4 errata: v1.0 includes all §X.Y Observability additions pinned in MANIFEST.supplementary_artifacts at release time; see soa

Readme

@soa-harness/runner

SOA-Harness Runner — HTTP surface, trust bootstrap, Agent Card, StreamEvents, permission resolver, attestation, audit, probes.

What it implements

Core profile of SOA-Harness v1.0. Exposes the normative /.well-known/agent-card.json, /.well-known/agent-card.jws, /health, /ready, /audit/tail, /audit/records, /permissions/resolve, /permissions/decisions, plus the M3-era observability endpoints (/memory/state/:sid, /budget/projection, /tools/registered, /events/recent, /observability/otel-spans/recent, /observability/backpressure, /logs/system/recent, /sessions/:id/state, /audit/sink-events).

Normative features:

  • §5 Required Stack + §5.3 External Bootstrap Root
  • §6 Agent Card + §7 Card Precedence
  • §10.3 Permission Decision flow + §10.3.2 pda-malformed / pda-verify-unavailable
  • §10.4 Handler Roles + §10.4.1 Autonomous→Interactive escalation
  • §10.5 Audit Chain (WORM sink mode, retention_class, reader-token scope)
  • §10.6 Handler Key Lifecycle (enroll, CRL poller, key-storage, SuspectDecision)
  • §11 Tool Registry + §11.3.1 dynamic test hook + §11.4 registered listing
  • §12 Session persistence + §12.5.3 crash-marker protocol + §12.6 resume paths
  • §13 Token Budget (M3 scope)
  • §14 StreamEvent (27-enum, §14.1.1 payloads, §14.5 observability endpoints)
  • §14.2 System Event Log + /logs/system/recent
  • §15 Hooks pipeline
  • §19.4 errata: v1.0 includes all §X.Y Observability additions pinned in MANIFEST.supplementary_artifacts at release time.

The spec pin is in the monorepo's soa-validate.lockspec_commit_sha is authoritative for exactly which schemas, fixtures, and normative sections this binary ships against.

Running

See create-soa-agent for the fastest start — it scaffolds a working Runner + Agent Card + tool registry + illustrative hook in one command.

The programmatic API exports startRunner, loadInitialTrust, BootOrchestrator, AuditChain, loadToolRegistry, CrlCache, InMemorySessionStore, generateEd25519KeyPair, and friends.

LLM Dispatcher (§16.3, v1.1+)

The Runner includes an LLM dispatcher wrapping provider-specific adapters. Adopter's job: implement ProviderAdapter for their chosen LLM; the dispatcher handles budget pre-check, billing-tag propagation, cancellation, retry budget, error classification, and audit.

Minimal wiring:

import { buildRunnerApp, Dispatcher, BudgetTracker, AuditChain } from "@soa-harness/runner";
import { ExampleProviderAdapter } from "@soa-harness/example-provider-adapter";

const adapter = new ExampleProviderAdapter({
  baseUrl: "https://api.openai.com/v1",
  apiKey: process.env.OPENAI_API_KEY!,
  name: "openai",
});

const dispatcher = new Dispatcher({
  adapter,
  budgetTracker: new BudgetTracker(),
  auditChain: new AuditChain(() => new Date()),
  clock: () => new Date(),
  runnerVersion: "1.1",
});

const app = await buildRunnerApp({
  // ... other opts
  dispatch: {
    dispatcher,
    sessionStore,
    clock: () => new Date(),
    runnerVersion: "1.1",
    bootstrapBearer: process.env.SOA_OPERATOR_BEARER, // optional — unlocks admin on /dispatch/recent
  },
});

Exposes:

  • POST /dispatch — fire one dispatch; session-bearer auth; schema-validated
  • GET /dispatch/recent — observability ring buffer; newest-first; session or admin bearer

For a real-provider scaffold showing request shaping + error classification

  • abort-signal handling, see @soa-harness/example-provider-adapter.

For conformance-probe fault injection (the InMemoryTestAdapter DSL), set SOA_DISPATCH_ADAPTER=test-double + SOA_DISPATCH_TEST_DOUBLE_CONFIRM=1 at Runner boot. The dispatcher auto-registers in test-double mode and exposes POST /dispatch/debug/set-behavior (admin-only).

See Core spec §16.3 / §16.3.1 / §16.4 / §16.5 for the normative contract and SV-LLM-01..07 for the conformance probes.

Conformance

Validate against the Go soa-validate harness:

soa-validate --agent-url http://localhost:7700 --profile core

For the scaffolded-agent flow: npm run conform inside a project produced by create-soa-agent auto-runs the validator.

To sanity-check validator-vs-Runner pin alignment before the full suite:

soa-validate --check-pins --impl-url http://localhost:7700

License

Apache-2.0.