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 🙏

© 2025 – Pkg Stats / Ryan Hefner

fsm

v1.0.2

Published

check finite state machine properties

Readme

fsm

check properties of finite state machines.

There is a lot of academic research in this area, yet this module is very simple. There are a lot of fancy tools available, but they are not easy to use. If idea is really useful, then I think a very simple tool should be viable.

License

MIT

Example

Define FSM as json, here is a stream with 4 states. This FSM expresses the constraint that the stream must not emit 'data' when paused, and also that it must not emit data after 'end'.

{
  START: {
    data   : 'START',
    pause  : 'PAUSED',
    end    : 'END',
    error  : 'ERROR'
  },
  PAUSED: {
    pause  : 'PAUSED',
    resume : 'START',
    error  : 'ERROR'
  },
  ERROR: {},
  END: {}
}

we can check a number of properties of this machine. does this machine halt? (and in the right place?) can you reach every state from every other?

API

validate (fsm)

check that all transitions are to defined states.

reachable (fsm)

calculate all states can reach each other states. the result is in the form of

{STATE1: {STATE2: [event path from S1 to S2]}}

terminal (fsm)

return the list of states that cannot reach another state.

alias: `deadlock'

livelock (fsm, [terminal])

get list of states that cannot reach a terminal state.

combine(fsm1, fsm2, start1, start2)

combine two fsm into one, obeying all the transitions in each. TODO: throw an error if there are transitions that are impossible in the combined machine.