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

@msm-core/jobs

v0.8.0

Published

Durable job/mission orchestration engine (CAS + idempotency state machine, cron missions, HITL approval). Pure decision logic; storage, queue, lock, clock injected via ports (no mongoose/bullmq/ioredis dependency).

Readme

@msm-core/jobs

Durable job / mission orchestration engine — a crash-safe state machine for long-running, resumable, human-gated agent work.

Pure decision logic over injected ports. The engine carries NO mongoose / bullmq / ioredis dependency (only jsonwebtoken, for resume tokens). Storage, queue, lock, clock and the step executor are supplied by the consumer via the interfaces in @msm-core/jobs/port — exactly the way @msm-core/memory keeps persistence out of its core. A platform writes thin adapters (e.g. Mongo + BullMQ + Redis) and gets durable jobs.

What it does

  • CAS + idempotency state machine — version-guarded compare-and-swap on every transition; an append-only step timeline keyed by a unique idempotency key. Crash-safe and exactly-once.
  • Wait + resumewaiting_time (delayed resume) and waiting_event (signed resume token, one-time-use nonce). A wait-reconciler re-enqueues due jobs as a durability backstop.
  • Pluggable workflows — declarative WorkflowDefinitions (data, not code) resolve each step.
  • Pluggable step executorrun_interaction_task runs whatever the consumer wires (e.g. an LLM agent turn); pure transitions (wait_time / complete / …) are no-ops.
  • HITL approval hook — a step can transition to awaiting_approval and resume on a decision.

Usage

import { createJobEngine, createWorkflowRegistry, DEFAULT_JOB_ENGINE_CONFIG } from "@msm-core/jobs";
import type { JobStore, QueuePort /* … */ } from "@msm-core/jobs/port";

const engine = createJobEngine({
  jobStore, queue, lock, nonce, ops, clock,         // your adapters (implement ./port)
  registry: createWorkflowRegistry(definitions),    // manifest-fed workflow definitions
  stepExecutor,                                     // run_interaction_task → your agent turn
  config: { ...DEFAULT_JOB_ENGINE_CONFIG, resumeToken: { secret, ttlSeconds: 86400 } },
});

await engine.orchestrateJobStep({ jobId, tenantId, reason: "create" });
await engine.reconcileWaitingTimeJobs(); // periodic durability backstop

The ports (JobStore.claim / finalizeStep / insertStep, QueuePort, LockPort, NoncePort, ClockPort, JobOpsPort, StepExecutorPort, WorkflowRegistry) are documented in port.ts. JobStore.insertStep must throw DuplicateStepError on a repeated idempotency key (the adapter maps its store's duplicate-key error onto it).