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

lmorchestrator

v0.1.1

Published

Mixed-model dynamic workflows for Sol, Luna, DeepSeek and Grok

Readme

LMO

Mixed-model dynamic workflows. A planner (Claude, Sol or Grok) writes a short JavaScript script; LMO runs it in the background across Sol, Luna, DeepSeek and Grok, each in its own git worktree. You watch the stave in the browser.

Install

From any git repo, with Bun on your PATH:

npx lmorchestrator

That is the whole setup. It writes a skill into .claude/skills/lmo/, starts the monitor on 127.0.0.1 and opens it. Same command as bunx lmorchestrator, or lmo after a global install.

Each repo runs its own server, on a port derived from the repo path, and prints that port and root on start. Runs always execute against the repo you launched them from. Override the port with LMO_PORT or a "port" in .lmo/config.json.

The package is not on the public registry yet. Until it is, from a clone of this repo:

bun install
bun link

Then lmo (or npx lmorchestrator once published) works in any project.

After that

Planners read the drop-in skill and run npx lmorchestrator themselves so the stave appears, then:

npx lmorchestrator workflow --script-path <file.js>

Script shape

export const meta = {
  name: "audit-routes",
  description: "Audit route handlers for missing auth",
}

phase("Find")
const found = await agent("List every route file under src/routes.", {
  worker: "sol",
  schema: { type: "object", required: ["files"], properties: { files: { type: "array", items: { type: "string" } } } },
})

phase("Audit")
const audits = await pipeline(found.output.files, (file) =>
  agent(`Audit ${file} for missing authentication checks.`, { worker: "luna", label: file }),
)

complete(audits.filter((row) => row && row.success))

Workers are a closed set: sol (medium), luna (max), deepseek (max), grok (high). apply(result) copies that agent's changed files into the parent tree. ask("…", { options: ["yes", "no"] }) parks the run and pings the planner.

Saved scripts live in .claude/workflows/<name>.js or ~/.claude/workflows/<name>.js.