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-cli

v0.2.0

Published

An 8-bit processor built from 2,161 NAND gates, run in your terminal. No dependencies.

Readme

stepper-cli

An 8-bit processor, built from 2,161 NAND gates and 167 flip-flops, running in your terminal.

npx stepper-cli

No wallet, no account, no network, no build step. It prints one line per clock edge: the instruction, the output port, the sixteen registers, the flags, and how many gates switched on that edge.

What it actually runs

Not a simulator of an instruction set. The netlist shipped in this package is the gate list a synthesis pass produced, and every cycle is computed by evaluating each of those gates in topological order and then latching every flip-flop at once. The instruction set is what falls out of the gates, not the other way round.

It is the same netlist the browser at https://steppercpu.tech loads and the same one a contract walks on chain, which is the point: the claim is checkable without taking anybody's word for it, including ours.

Usage

stepper                            forty cycles of the default program
stepper --prog selftest             the self-test, to its halt
stepper my.asm --in 42              your own program, your own input byte
stepper my.asm --cycles 500 --quiet

| Flag | | |---|---| | --prog <name> | one of the programs built into the package | | --in <byte> | the value on the input port | | --cycles <n> | how many clock edges to take | | --quiet | the final state only |

Verifying a chip on chain

npx stepper-cli verify 0x…

Reads every cycle a deployed chip has logged, replays each one on the netlist in this package, and checks that every output matches and that the final state equals the chip's own snapshot(). This is the one command that uses the network.

If the default RPC endpoint cannot be reached from your network, name another one for the same chain. The replay does not depend on which:

npx stepper-cli verify 0x… --rpc https://steppercpu.tech/rpc

Writing a program

        ldi  r2, #0
loop:   in   r0
        add  r2, r0
        out  r2
        jmp  loop

Assemble and run it with stepper that.asm. The assembler is the same one the browser uses.

Requirements

Node 20 or newer. No dependencies, at all.

Licence

Apache-2.0. See LICENSE, and NOTICE for what the licence does not grant.