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

@paleo/openclaw-qa-runner

v0.4.1

Published

Dockerised regression-test harness for OpenClaw workspaces: bus, scenario driver, judge, Compose stack.

Readme

@paleo/openclaw-qa-runner

Dockerised regression-test harness for OpenClaw workspaces. Drives the agent through two synthetic channels (discord-mock, slack-mock) and asserts the results.

Pair with @paleo/openclaw-channel-mock-core, @paleo/openclaw-discord-mock, @paleo/openclaw-slack-mock.

For internals (topology, Dockerfile pair, mocked-CLI shim, channel plugin mechanics, OpenClaw quirks), see openclaw-qa-architecture.md.

Install

npm i -D @paleo/openclaw-qa-runner @paleo/openclaw-channel-mock-core @paleo/openclaw-discord-mock @paleo/openclaw-slack-mock openclaw

Requires Docker Compose v2.20+ (overlay uses Compose include:).

Wire package.json scripts:

"scripts": {
  "env:build": "openclaw-qa-runner env build",
  "env:up":    "openclaw-qa-runner env up",
  "env:down":  "openclaw-qa-runner env down",
  "qa":       "openclaw-qa-runner qa"
}

Init

npx @paleo/openclaw-qa-runner init <qa-dir>

Drops four files:

  • openclaw.json — gateway config (mode local, both channel plugins enabled, main agent placeholder).
  • .env.local.example — copy to .env.local, fill ANTHROPIC_API_KEY + OPENCLAW_WORKSPACE_DIR.
  • docker-compose.yml — thin overlay that include:s the base from node_modules/.
  • Dockerfile — consumer-owned. Inherits the base via FROM paleo/openclaw-qa-runner-base:${QA_RUNNER_BASE_TAG}. Add RUN/COPY/ENV for consumer-specific setup (extra system packages, skills install, etc.).

Configure

Edit openclaw.json:

  • agents.list[id=main].model — LiteLLM-style provider/model ref. The template ships a placeholder; OpenClaw fails loudly until you pick one.
  • agents.list[id=main].workspace — host path to your OpenClaw workspace, bind-mounted into the gateway. Field name is workspace, not workspaceDir.
  • channels.* — both discord-mock and slack-mock blocks point at the same bus.

Drop scenarios under scenarios/<id>.ts. Project fixtures under projects-fixture/ (bind-mounted to ~/projects/ in the gateway).

Scenarios are loaded by Node 24's built-in TypeScript stripping. Stick to the strip-compatible subset (no enum, namespace, decorators, ctor parameter properties, import =). Shared helpers go under scenarios/_lib/discoverScenarios() skips directories.

Env vars (.env.local)

Required:

  • ANTHROPIC_API_KEY
  • OPENCLAW_WORKSPACE_DIR — host path mounted at /home/claw/.openclaw/workspace.

Optional (defaults relative to the consumer's qa/ dir):

  • OPENCLAW_CONFIG_PATH./openclaw.json
  • QA_PROJECTS_DIR./projects-fixture
  • QA_SCENARIOS_DIR./scenarios
  • QA_ARTIFACTS_DIR./artifacts
  • QA_GATEWAY_LOGS_DIR./.gateway-logs
  • OPENCLAW_RAW_STREAM=1 — also write raw-stream.jsonl alongside the always-on anthropic-payload.jsonl.

QA_PROJECT_DIR, QA_RUNNER_PACKAGE_DIR, CLAW_UID, CLAW_GID are injected by the CLI.

Run

npm run env:build                                                  # build base + consumer image
npm run env:up                                                     # bring up bus + gateway (both channels register)
npm run qa -- --channel all <scenario>                             # one scenario, both channels
npm run qa -- --channel all --all                                  # every scenario, both channels
npm run qa -- --channel discord-mock <scenario>                    # restrict to one channel
npm run qa -- --channel all --iterations 5 <scenario>              # repeat each (scenario, channel) pair 5×
npm run qa -- --channel all --iterations 5 --max-failures 1 <s>    # abort a pair after >1 failure
npm run env:down

env:build first builds the base image (paleo/openclaw-qa-runner-base:<pkg-version>) from this package's Dockerfile.base, then builds the consumer image. Layer cache makes repeat base builds near-free; env:up / qa skip the base build when the tag already exists.

Rebuild required after: bumping any @paleo/openclaw-* dependency, edits to openclaw.json, or any change to the consumer Dockerfile.

Scenarios run serially through one gateway. Exit 0 iff every pair passes.

Scenario primitives

From @paleo/openclaw-qa-runner (src/context.ts):

  • channel, conversationId, accountId — per-task isolation. Use ctx.conversationId everywhere; never hard-code a value.
  • sendInbound(input) — push an inbound on the bus.
  • poll, waitForOutbound, expectNoOutbound — bus consumers.
  • assertRegex, assertEqual, assertLength — structural assertions.
  • judgeLLM({ message, rubric, label }) — Anthropic-direct judgement (no bus traffic, no gateway).
  • mockCli(name, handler) — intercepts the gateway's calls to git / npm / pnpm / yarn / claude. Unregistered calls fail the scenario with failure.source = "cliMock".
  • log, getCursor.

Prefer structural assertions over judgeLLM; reserve the judge for free-form content claims.

Judge model

Defaults to anthropic/claude-haiku-4-5. Override via QA_JUDGE_MODEL on the runner service (set in your consumer overlay). The ref must be LiteLLM-style; only the anthropic/ provider is wired up today. The judge is not an OpenClaw agent — don't configure it in openclaw.json.

Artifacts

artifacts/<runStamp>/<scenario>-<channel>[-<NN>][-<VERDICT>]/:

  • events.jsonl — appended live, survives a runner crash.
  • report.json — final ScenarioReport. Merges events.jsonl with agentToolCall entries from the gateway payload log; adds per-scenario cost.

<NN> is the iteration index (omitted when --iterations 1). <VERDICT> is PASS / FAIL, applied by renaming the directory after report.json is written. A directory with no verdict suffix means the run is pending or crashed before rename.

Authoritative types: src/report.ts.

Channels

Both discord-mock and slack-mock register on every boot. Pick which to drive per scenario via --channel discord-mock|slack-mock|all.

  • discord-mock — full Discord-shaped surface; thread-create posts an optional body atomically.
  • slack-mock — restricted Slack-shaped surface (react / read / edit / delete / reactions / search). Bare-channel inbounds auto-thread on the triggering message.

Inbound metadata claims Provider / Surface / OriginatingChannel = the registered channel id so the SDK routes tool-schema discovery to the right plugin. Assert on conversation.id / threadId, not envelope formatting.

Target format

Canonical destination param is to. Accepted shapes:

  • channel:<id> or bare <id> (channel)
  • dm:<id>
  • group:<id>
  • thread:<channelId>/<threadId>

Actions resolve to → target → channelId.

Attribution

The runner package contains no upstream-adapted code. See sibling packages' NOTICE.md for OpenClaw attribution covering the channel plugins.