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/pipeline

v0.3.6

Published

Install loom in one step: npm i -g @loomfsm/pipeline && loom setup. Pulls the CLI, the MCP server, the default bundle, and the zero-config provider.

Downloads

839

Readme

@loomfsm/pipeline

One-step install for the loom pipeline. Installing this package puts the loom command on your PATH and pulls everything the pipeline needs to run: the command-line installer, the MCP server, the default code bundle, and the zero-config provider.

Install

npm i -g @loomfsm/pipeline

Set up your agent host

loom setup           # register the MCP server + install the /task and /done commands
loom allowlist add   # authorize the current project for tasks (run once per project)

loom setup writes the MCP server registration and drops the /task and /done slash commands into your host's command directory. It is idempotent — re-running it changes nothing and never clobbers a command you have edited (use --force to overwrite). Pass --project to scope the install to the current directory instead of your user profile, or --dry-run to preview the changes.

The project allowlist is default-deny by design: the server never enrolls a project on its own, so each directory you want to use must be authorized once with loom allowlist add.

Run a task

In an authorized project, from your agent host:

/task fix the typo in the module header comment

The host runs each spawned agent with the prompt the server provides, surfaces each approval gate for your decision, and drives the work to completion. Then /done shows the summary.

Commands

loom setup [--user|--project] [--dry-run] [--force]
loom allowlist add [path] [--dry-run]
loom allowlist list
loom init [--dry-run]
loom --help | --version

License

Apache-2.0