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

stepper-sdk

v0.1.0

Published

The STEPPER ST-8 processor as a library: 2,161 NAND gates, an assembler, and a verifier that replays a chip's whole on-chain history and checks it.

Readme

stepper-sdk

The STEPPER ST-8 processor, as a library: 2,161 NAND gates and 167 flip-flops, evaluated one clock edge at a time.

npm i stepper-sdk

Run a program

const stepper = require("stepper-sdk");

const { rom } = stepper.assemble(`
  loop:  in   r0
         out  r0
         jmp  loop
`);

const r = stepper.run(rom, { cycles: 12, inValue: 42 });
console.log(r.out, r.cycles, r.gates);

run() evaluates the shipped gate list in topological order and latches every flip-flop at once. It is not a model of an instruction set: the instruction set is what falls out of the gates.

Verify a chip on chain

const result = await stepper.verify("0x…");
console.log(result.ok, result.cyclesReplayed);

A chip is deterministic and all of its inputs are public. program() returns its ROM; every step() emits Stepped(sponsor, cycle, outPort, inValue). ROM plus those events is the complete tape the machine ran on, so verify() fetches both, replays the whole history on the netlist in this package, and checks two things:

  • the final cycle, program counter, output and flags match snapshot()
  • every logged output matches, cycle by cycle, not just the last one

Nothing in that calculation trusts us. The netlist is here, the events come from whatever node you name, and the arithmetic happens on your machine.

What is not here

No launch function, no signer, no key handling. This package reads and computes. It cannot spend.

API

| | | | --- | --- | | assemble(source) | ST-8 assembly to a ROM | | run(rom, opts) | run it on the netlist | | programs() | the shipped programs, as source | | readChip(addr, opts) | cycle, pc, out, flags, registers, ROM | | history(addr, opts) | every Stepped event, in cycle order | | decodeStepped(log) | one raw log to its fields | | verify(addr, opts) | replay the history and check the chain agrees | | Machine, loadNetlist | the evaluator, for building your own loop |

opts.rpc names the node. It defaults to Robinhood Chain mainnet.

Licence

Apache-2.0. The name and marks are reserved under section 6; see NOTICE.