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

@obep/sdk

v0.1.0

Published

Thin, framework-agnostic OBEP client for the customer's app — relay.run(task) with a live status stream. Apache-2.0.

Readme

@obep/sdk

The thin client for driving OpenErrand / OBEP tasks from your app — run real browser actions inside your end user's own browser, logged in as them. Framework- and runtime-agnostic (browser or Node).

npm install @obep/sdk

Quickstart

import { RelayClient } from "@obep/sdk";

const client = new RelayClient({
  url: "wss://relay.openerrand.app",
  apiKey: process.env.OPENERRAND_API_KEY, // server-side only
});

// Run a task under a signed playbook, targeting a paired user.
const run = client.run({
  url: "https://portal.example.com/login",
  userId: "dana",
  playbookId: "acme.portal-upload",
  decide,                        // your LLM — only used on the LLM-fallback path
});

// A TaskRun is BOTH a live status stream...
for await (const status of run) {
  console.log(status.phase, status.detail ?? "");
}

// ...and awaitable for the final result.
const { confirmationNumber } = await run;

API

new RelayClient({ url, apiKey?, WebSocketImpl? })

  • url — the relay WebSocket endpoint (wss://…).
  • apiKey — your tenant API key. The relay derives the tenant from it; keep it server-side. Required for multi-tenant routing.
  • WebSocketImpl — a WebSocket constructor. Defaults to the browser's WebSocket; in Node, pass the ws package:
    import { WebSocket } from "ws";
    new RelayClient({ url, apiKey, WebSocketImpl: WebSocket });

client.run(task) → TaskRun

task: { url, userId?, playbookId?, decide, taskId?, onStatus? }.

  • decide(ctx) turns each PageContext into the next Command — your intelligence (an LLM, or a stub). It's unused when a fully deterministic playbook drives the task.

A TaskRun is a PromiseLike (await it for the result bag) and an AsyncIterable<StatusMessage> (iterate it for live status). A terminal error status ends the stream and rejects the result.

How it fits

Credentials never flow through this SDK or the relay — fillSecret carries only a vault key reference, resolved on the user's device. (A document you upload does ride the command path; source it locally where you can.) See the integration guide and the security model.

Apache-2.0.