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

lispex

v1.4.0

Published

Local CLI for the Lispex reference interpreter and Lispex Vouch artifact checks. Evaluates .lspx files, verifies receipts and bridge reports, and replays decision corpora; no codegen.

Readme

lispex

A local command-line runner for Lispex — a thin wrapper around the same WebAssembly reference interpreter the browser playground at lispex.com runs. Same core, same results: a program evaluates identically on the CLI and in the browser.

It is an interpreter and Lispex Vouch artifact checker only. Conversion to other languages, where available, is a separate commercial path and is not part of this reference CLI.

Install

npm install -g lispex

Use

lispex run hello.lspx       # evaluate a file, print its output
lispex hello.lspx           # shorthand for "run"
echo '(+ 1 2 3)' | lispex    # evaluate source from stdin
lispex verify receipt.json   # check a CSK differential receipt artifact
lispex replay gallery --against 1.2.16
                              # compare a decision gallery against a version pin
lispex --version
lispex --help

Exit code is 0 on success, 1 on an evaluation error or artifact mismatch, and 2 on usage/I/O/JSON errors. Diagnostics (E3xx/W3xx, recursion-limit, …) are written to stderr in the same format the playground shows.

$ echo '(define (fact n) (if (= n 0) 1 (* n (fact (- n 1))))) (fact 100)' | lispex
93326215443944152681699238856266700490715968264381621468592963895217599993229915608941463976156518286253697920827223758251185210916864000000000000000000000000

How it works

The CLI loads the wasm-pack (--target nodejs) glue and calls run_lispex(src), which reads → normalizes → evaluates each top-level form and returns { output, diagnostics, ok }. It implements no evaluation of its own — the WebAssembly module is the reference, so browser/local equivalence is preserved for free (arbitrary-precision integers, call/cc, multiple values, the deterministic numeric tower, and the wasm recursion bound all behave identically).

The verify and replay commands are the Lispex Vouch path. They do not load the WebAssembly module or execute source. They perform offline artifact-consistency checks over existing csk.differential-receipt/v0 JSON receipts and decision gallery directories.

License

Apache-2.0