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

workblock-factory

v0.2.0

Published

Workblock runtime CLI: install, run, upgrade, diagnose, and repair the Beyond Work local developer and agent stack. Supersedes the 0.1.x .mjs-based installer.

Readme

workblock-factory

Workblock runtime CLI: install, run, upgrade, diagnose, and repair the Beyond Work local developer and agent stack — the platform bridge, the VS Code / Cursor extension, the headless Claude Code / Codex bridge, the local sandbox runtime, digest-pinned Docker images, and versioned knowledge bundles — from one npm-installed command.

Install

npm install -g workblock-factory

Requires Node >= 22.5. The docker and fidelity sandbox modes additionally need Docker with Compose v2 and Docker Hub access to the private autoswarm/* images.

Quickstart

# Claude Code user without VS Code: headless bridge + docker sandbox.
workblock setup --profile claude --bridge headless --sandbox docker

# Verify everything (add --deep for network dials and service probes).
workblock --health

# Launch Claude Code with the Beyond Work MCP config and bridge preflight.
bw-claude

State lives under .bw-sandbox/ in your workspace root; inspect it with workblock status, workblock config get, and workblock doctor.

Binaries

| Bin | Purpose | | --- | --- | | workblock | Runtime CLI: setup, status, health, upgrade, doctor, bridge, platform, sandbox, agents, vscode, knowledge, images, config, version | | workblock-factory | Alias for workblock (continuity with the 0.1.x installer) | | bw-claude | Launch Claude Code with generated BW config and a live bridge | | bw-codex | Launch Codex with a generated BW profile and a live bridge | | beyondwork-agent | MCP stdio server bridging agents to the Workblock bridge |

Top-level aliases: workblock --health, workblock --upgrade, workblock --bridge-restart.

Documentation

Source and docs: https://github.com/chllming/workblock-factory

Development

From packages/workblock-cli in the repository:

pnpm test          # vitest suite
pnpm check-types   # tsc --noEmit
pnpm build         # esbuild bundles into dist/ (CJS, one file per bin)
pnpm dev -- --help # run the CLI from source via tsx

The canonical MCP tool registry lives in the sibling @beyondwork/workblock-bridge-core package (synced from the private Beyond Work monorepo); after a registry sync, run pnpm generate there to refresh the generated docs table, or the registry drift tests will fail.