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

@braidhq/cli

v0.4.2

Published

Command-line entry point for Braid.

Readme

@braidhq/cli

Braid keeps a product's intent and its code aligned in one knowledge graph. @braidhq/cli is the braid command, the terminal front door for scaffolding a workspace and running the stack locally.

Role

The entry point a user reaches for first. It scaffolds a workspace and boots the stack without any hand-wiring, then gets out of the way. It owns no logic of its own; each command is a thin shell over the server or the filesystem.

  • Scaffold: braid init lays down a workspace template on disk.
  • Run: braid serve boots the server, braid dev runs the server and Studio together for local development.
  • Inspect: braid workspace list queries a running server over HTTP.

Commands

  • braid init <dir> scaffolds a workspace template. Options: --ontology (default ddd), --name (default the directory basename), --force to overwrite an existing PRODUCT.md.
  • braid serve runs the server. --port defaults to 4321.
  • braid dev runs the server and Studio together. In a monorepo checkout it spawns both dev processes so edits reload live; standalone it runs the server only. --port sets the server port, Studio stays on 5173.
  • braid workspace list lists the workspaces on a running server. --api defaults to http://localhost:4321.

Structure

src/
├── main.ts            cac command definitions, the braid binary
└── commands/
    ├── init.ts        scaffold a workspace template on disk
    ├── serve.ts       boot the server via the server package's startServer
    ├── dev.ts         run server and Studio, monorepo or standalone
    └── workspace.ts   query a running server over HTTP

Boundaries

  • Orchestrates, does not implement. serve delegates to @braidhq/server's startServer, so env loading, graceful shutdown, and background recovery match the server binary exactly. init only writes files. workspace talks to a server over HTTP.
  • Does not register a workspace. init lays down the template on disk. Registration with a server is a Studio Wizard flow, not a CLI step.
  • Holds no state. Nothing here persists between invocations.

Dependencies

  • @braidhq/server for startServer and root env loading, so serve and dev share the server's boot path.
  • cac for command parsing, picocolors for terminal colour.