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

petri-ts

v0.1.5

Published

A lightweight TypeScript Petri net engine

Readme

petri-ts

A small TypeScript Petri net engine. Define places and transitions, fire them, analyse reachable states, or wire up a load/fire/save dispatcher for production use.

For background on Petri nets and the ideas behind this library, see the blog post.

Install

npm install petri-ts

Quick start

import { type PetriNet, fire, reachableStates, terminalStates } from "petri-ts";

type Place = "idle" | "running" | "done";

const net: PetriNet<Place> = {
  transitions: [
    { name: "start", inputs: ["idle"], outputs: ["running"] },
    { name: "finish", inputs: ["running"], outputs: ["done"] },
  ],
  initialMarking: { idle: 1, running: 0, done: 0 },
};

let m = net.initialMarking;
m = fire(m, net.transitions[0]); // { idle: 0, running: 1, done: 0 }

reachableStates(net);  // all reachable markings from initialMarking
terminalStates(net);   // markings where nothing can fire

Dispatcher

For the "marking as a JSON column" pattern — one net definition, one row per instance, load/fire/save inside a transaction:

import { createDispatcher, memoryAdapter } from "petri-ts";

const d = createDispatcher(net, memoryAdapter());
await d.create("order-1");
await d.dispatch("order-1", "start");
const { marking } = await d.inspect("order-1");

memoryAdapter() is a Map-backed store for tests. In production, write your own PersistenceAdapter that wraps your database — the lib doesn't handle locking, your transaction does.

Analyse

Run all analysis in one call — reachable states, terminal states, deadlock check, invariant verification, and optional DOT output:

import { analyse } from "petri-ts";

const result = analyse(net, {
  invariants: [
    { weights: { idle: 1, running: 1, done: 1 } },
  ],
  dot: true,
});

result.reachableStateCount; // 3
result.terminalStates;      // [{ idle: 0, running: 0, done: 1 }]
result.isDeadlockFree;      // false (done is terminal)
result.invariants[0].holds; // true (tokens conserved)
result.dot;                 // Graphviz DOT string

API

| Function | Description | |---|---| | canFire(marking, transition) | Check if a transition is enabled | | fire(marking, transition) | Fire a transition, returns new marking | | reachableStates(net) | BFS all reachable markings | | terminalStates(net) | Reachable markings with no enabled transitions | | isDeadlockFree(net) | True if no terminal states exist | | enabledTransitions(net, marking) | Which transitions can fire | | checkInvariant(net, weights) | Verify a weighted token sum is constant | | analyse(net, options?) | All-in-one analysis: states, deadlocks, invariants, DOT | | toDot(net, marking?) | Graphviz DOT output | | createDispatcher(net, adapter) | Load/fire/save dispatcher | | memoryAdapter() | In-memory persistence for tests |

Dev

bun test        # vitest
bun run build   # JS bundle + .d.ts
bun run lint    # oxlint
bun run fmt     # oxfmt