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

defuss-orchestrator

v0.1.2

Published

Federated pull-based work orchestrator with rendezvous hashing, sticky ownership, async durability, and pluggable worker/work selection.

Readme

defuss-orchestrator

NOT RELEASED YET. -> Test with browser extension!

TODO: Better docs etc., better test coverage. More realistic examples with long-running workers, snapshots, and durable state. Chaos testing with simulated worker and network failures.

Federated pull-based orchestration with:

  • sticky ownership chosen by rendezvous hashing at schedule time
  • async durability via buffered append log + snapshots or DB adapter
  • worker pull topology only
  • pluggable work selection and worker scoring
  • tiny metrics sink interface

Install

npm install defuss-orchestrator

Basic usage

import {
  createOrchestrator,
  createJsonFileDurableStore,
} from "defuss-orchestrator";

const orchestrator = createOrchestrator({
  self: { id: "peer-a", endpoint: "http://127.0.0.1:3000" },
  durableStore: createJsonFileDurableStore({
    dir: "./tmp/orchestrator-a",
    flushThrottleMs: 50,
  }),
});

await orchestrator.start();
orchestrator.upsertPeer({ id: "peer-a", endpoint: "http://127.0.0.1:3000", incarnation: 1 });

const scheduled = orchestrator.schedule({
  id: "work-1",
  type: "image-render",
  payload: { prompt: "nebula" },
  payloadBytes: 22,
});

if (scheduled.kind === "accepted") {
  const lease = orchestrator.leaseNextWork({
    worker: {
      id: "worker-1",
      capabilities: ["image-render"],
      inflight: 0,
      telemetry: { cpuLoad: 0.2 },
    },
  });

  if (lease.kind === "leased") {
    orchestrator.reportCompleted({
      id: lease.workItem.id,
      workerId: "worker-1",
      result: { success: true, result: { imageId: "img-1" } },
    });
  }
}

Notes

  • The engine is deliberately sticky-owner after accept. Rendezvous hashing is used for initial placement only.
  • Wrong peers can suggest an owner by hash, but they cannot always prove the accepted owner after membership churn without replicated responsibility data.
  • Terminal and abandoned items leave hot memory. Optional tombstones exist for a short TTL to absorb late worker replies and status polls.

See ARCH.md for the guarantees and trade-offs.