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

@nodetool-ai/kernel

v0.8.2

Published

Workflow kernel: Graph model, NodeInbox, and Actor runtime

Readme

@nodetool-ai/kernel

The workflow kernel: the Graph model, NodeInbox, the actor runtime, and WorkflowRunner. Executes a workflow graph via message-passing between node actors. The graph is acyclic except for loops that close on a Loop node.

Responsibilities

  • Graph — structural model + validation (edge endpoints, types, source handles).
  • NodeActor / NodeInbox — correlation-aware, buffered scheduling.
  • WorkflowRunner — drives a run, emits ProcessingMessages, collects outputs.

Untaken branches

A node wired to data inputs that receives nothing on any of them does not run. Its upstreams closed without emitting — an If emits only the taken handle, a filter can emit nothing — so the node is on a branch nobody took. Skipping it closes its own outputs with nothing, which cascades down the untaken subgraph.

Partial input still fires: a node that got a value on one handle and nothing on another runs, with the declared default filling in the empty handle.

Loops

A cycle is valid only when it closes on the next or condition input of a nodetool.control.Loop node. Correlation analysis leaves those back edges out of the topological order and gives the loop body its own iteration scope. The Loop runs in its own actor mode (src/loop.ts) and closes its iteration outputs itself, because the body's EOS cannot reach it first. For graphs with a Loop, the runner reports a quiescent graph (every actor parked on its inbox) so a Loop can end runs whose body stopped feeding back. Design: docs/workflow-loops.md.

Usage

import { WorkflowRunner } from "@nodetool-ai/kernel";

const runner = new WorkflowRunner("job-1", { resolveExecutor });
const result = await runner.run({ job_id: "job-1", params }, { nodes, edges });

Develop

npm run build --workspace=packages/kernel
npm run test  --workspace=packages/kernel
npm run lint  --workspace=packages/kernel

Scheduling design: docs/correlation-design.md.