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

@stateful-spec/flow

v0.1.0

Published

Validated state-transition CLI for the Stateful Spec multi-agent flow (flow-state.md). Cross-platform, zero runtime dependencies.

Readme

@stateful-spec/flow

A small cross-platform, zero-runtime-dependency Node/TypeScript CLI that is the single writer of .stateful-spec/flow-state.md for the Stateful Spec multi-agent flow. It is the Node twin of the Rust crate stateful-spec-flowidentical verbs, state-file contract, and exit codes (parity is enforced by a shared conformance suite). Instead of agents hand-editing YAML, they call validated verbs: each checks its precondition, mutates the state atomically, bumps a monotonic seq, and appends a turn-log line. Illegal transitions are rejected and leave the state untouched.

Optional. The methodology works without this tool — the tooling contract can be satisfied by any implementation or by relaying turns by hand. An agent guided by the methodology must ask the user's permission before using it.

Install

npm install -g @stateful-spec/flow      # provides the `flow` command

Verbs

| Group | Verbs | |-------|-------| | PM | approve-plan --total <n> · spec-ready · approve · request-changes "<reason>" · block "<reason>" · submit-spec (three-agent) | | Architect | approve-spec · request-spec-changes "<reason>" (design gate) | | Engineer | submit [--gate "k=v …"] · advance [--allow-dirty] · hand-back "<reason>" | | Utility | status · poll --role <pm\|engineer\|architect> [--interval N] [--timeout N] [--stall-after N] [--once] · spawn |

Exit codes — transitions: 0 ok · 1 precondition/gate refused · 2 usage · 3 IO. poll: 0 your turn · 1 DONE · 2 BLOCKED · 3 IO · 4 timeout · 5 waiting (--once).

advance refuses on a default branch and while product code (outside .stateful-spec/) is uncommitted, and archives the completed milestone's auxiliaries via git mv. --allow-dirty bypasses.

spawn — configurable, tool-agnostic

flow spawn launches the next agent. The tool is agnostic: it resolves the spawn kind from the flow step (commit | arch-review | engineer) and runs a command template the project supplies in .stateful-spec/flow.conf. Nothing about any agent runner or persona is hardcoded.

# .stateful-spec/flow.conf
[spawn]
program     = my-agent-runner
arch_review = run "/my-architect {profile} {verdict_directive}" {spec}
engineer    = run "/my-engineer {profile}" {handoff}
commit      = run /my-commit

[git]
default_branches = main, master

Placeholders: {role} · {profile} · {spec} · {handoff} · {verdict_directive}. A token that resolves to empty is dropped. With no template configured for a kind, spawn fails with guidance — every other verb still works.

Build & test

npm install
npm test        # tsc + node --test

Node ≥ 18. Zero runtime dependencies; built with TypeScript. MIT licensed.