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

@sbo3l/inngest

v1.2.0

Published

Inngest durable-workflow adapter for SBO3L — gate each payment-shaped step through the policy boundary, with replay-safe audit anchoring.

Readme

@sbo3l/inngest

Durable-workflow adapter for SBO3L. Gates each payment-shaped step through the policy boundary, with replay-safe audit anchoring.

npm i @sbo3l/inngest @sbo3l/sdk inngest

Wiring

import { Inngest, NonRetriableError } from "inngest";
import { SBO3LClient } from "@sbo3l/sdk";
import { gateAprp, PolicyDenyError } from "@sbo3l/inngest";

const inngest = new Inngest({ id: "agent-runner" });
const sbo3l = new SBO3LClient({ endpoint: "http://sbo3l:8730" });

export const swap = inngest.createFunction(
  { id: "agent.swap" },
  { event: "agent/swap.requested" },
  async ({ event, step }) => {
    try {
      const receipt = await gateAprp(step, sbo3l, event.data.aprp);
      await step.run("execute-swap", () => doSwap(event.data, receipt));
    } catch (e) {
      if (e instanceof PolicyDenyError) {
        // Inngest treats throws as retries; wrap to skip retries on deterministic deny.
        throw new NonRetriableError(e.message);
      }
      throw e;
    }
  },
);

Why a wrapper instead of raw step.run

Inngest persists each step.run result. On a workflow retry, the persisted result replays — handler doesn't re-execute. gateAprp makes this work for SBO3L by:

  1. Wrapping submit in step.run("sbo3l.submit:<task_id>", ...) so the receipt is journaled.
  2. Returning a non-throwing union from the inner handler so the deny envelope is also journaled (otherwise an exception would re-throw on every retry, re-fetching the daemon and tripping protocol.nonce_replay).
  3. Re-throwing as PolicyDenyError AFTER replay so the caller can wrap with NonRetriableError — denies are deterministic; retrying is wasteful.

gateAprpSafe — no-throw variant

const r = await gateAprpSafe(step, sbo3l, aprp);
if (r.ok) await doExecution(r.receipt);
else logDeny(r.decision, r.deny_code, r.audit_event_id);

Use when the workflow has its own deny-handling branch and shouldn't fall through to Inngest's retry / NonRetriable handling.

Tests

npm test         # 10 vitest passing
npm run typecheck
npm run build