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

@zebric/runtime-simulator

v0.3.1

Published

Browser-only Zebric simulator runtime

Readme

@zebric/runtime-simulator

Browser-only simulator runtime for Zebric blueprints.

This package is intended for development previews and embedded authoring tools. It keeps data in memory, simulates accounts and plugins, and avoids real network calls by default.

Usage

import { ZebricSimulatorRuntime } from '@zebric/runtime-simulator'

const runtime = new ZebricSimulatorRuntime({
  blueprintToml,
  seeds: {
    demo: {
      Task: [{ id: 'task-1', title: 'Review plan' }],
    },
  },
  initialSeed: 'demo',
  initialAccount: 'manager',
  pluginPolicy: { defaultLevel: 1 },
  apiPolicy: { mode: 'debug' },
})

const page = await runtime.render('/')

const webhook = runtime.triggerWebhook('/notifications/slack_ops/actions', {
  action_id: 'dispatch_approve',
  value: 'task-1',
  user_id: 'U123456',
})

Current Scope

  • In-memory entity storage
  • Seed switching and reset
  • Simulated accounts: user and manager by default
  • Core RequestHandler and HTMLRenderer integration
  • Client-style form submission through submit(...)
  • Workflow debug history and manual workflow triggering
  • Workflow inbound webhook triggering through triggerWebhook(...)
  • Audit log capture for page reads, mutations, denied access, account switches, workflow triggers, and webhook triggers
  • Simulated Slack, email, notification, and webhook integration outbox
  • Plugin level 0 and level 1 simulation
  • Simulated REST/API call logging with optional mocks

Workflow notify, email, and webhook steps are captured in memory. No Slack message, email, webhook request, or API request is sent by the simulator.

This runtime is not a security boundary and should only be used for preview/development workflows.