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

@loomfsm/cli

v0.3.6

Published

The loom command-line installer — register the MCP server and authorize projects.

Readme

@loomfsm/cli

The loom command-line tool. It registers the pipeline MCP server with your agent host, installs the /task, /done, and /proceed slash commands, authorizes project directories, and inspects or drives the active task.

Most users install the @loomfsm/pipeline meta-package, which bundles this CLI together with the server, the default bundle, and the provider in a single npm i -g. Install this package directly only if you are assembling your own runtime.

Commands

loom setup [--user|--project] [--dry-run] [--force]
    Register the MCP server and install the /task, /done, and /proceed commands.
    --user      install for your user (default): ~/.claude.json + ~/.claude/commands/
    --project   install for this project only:  ./.mcp.json + ./.claude/commands/
    --dry-run   print what would change without writing anything
    --force     overwrite a divergent registration or a locally-edited command

loom allowlist add [path] [--dry-run]
    Authorize a project directory for tasks (default: current directory).

loom allowlist list
    Show the authorized project directories.

loom init [--dry-run]
    Ensure this project's .claude/ exists, authorize it, then point at /task.

loom reset [path] [--force] [--dry-run]
    Archive this project's finished task into .claude/history/ and free the slot
    for the next one. An in-progress task is refused unless --force is given.

loom history [path]
    List the archived tasks for this project.

loom status [path]
    Show the active task: its status, where in the flow it sits, any pending
    agents and how long they've waited. Flags a stalled task (a likely dropped
    transport) — resume it with /proceed.

loom run "<task>"
    Drive a task to its end non-interactively, executing each spawn with a
    configured provider instead of a host. Pauses and prints a human gate
    rather than answering it. Needs an async provider configured for the project.

loom --help | --version

Setup is idempotent: re-running changes nothing and never clobbers a command you have edited. The project allowlist is default-deny and operator-authored — the server never enrolls a directory on its own.

License

Apache-2.0