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

@acoyfellow/lab-cli

v0.0.2

Published

Minimal CLI for Lab — agents shell out, get traces back

Readme

@acoyfellow/lab-cli

Minimal CLI for Lab. Agents shell out, get traces back.

Install

npm install -g @acoyfellow/lab-cli

Usage

# Run JS in a single isolate
lab run 'return 1 + 1'

# Run a multi-step chain
lab chain '[{"body":"return [1,2,3]","capabilities":[]},{"body":"return input.map(n=>n*2)","capabilities":[]}]'

# Spawn nested isolates
lab spawn 'const a = await spawn("return 10", []); return a'

# AI generates code from a prompt, then runs it
lab generate 'Sum the numbers 1 to 10'

# Fetch a stored trace
lab trace abc123

# Seed demo KV data
lab seed

Every command prints JSON to stdout. Every run includes a traceId pointing to the permanent trace.

Environment

| Variable | Default | Description | |----------|---------|-------------| | LAB_URL | http://localhost:1337 | Lab Worker origin |

For agents

An agent shells out to lab, reads the JSON result, and uses the traceId as proof of execution:

result=$(lab chain '[{"body":"return 42","capabilities":[]}]')
traceId=$(echo "$result" | jq -r '.traceId')
# traceId is now a permanent, inspectable artifact

Or from a script:

lab run 'return { computed: Math.pow(2, 32) }' | jq '.result'

Built with Effect

Internals use Effect v4 for structured error handling. The CLI interface is just stdin/stdout — Effect stays inside.

License

MIT