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

@xplainer/cli

v0.0.9

Published

The xplainer local runtime: the `xplainer` binary, its always-on daemon, and the HTTP and MCP server core they serve.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

brewmytechbrewmytech

Keywords

Readme

@xplainer/cli

The xplainer local runtime. It installs the xplainer binary, which serves the eight explainer tools to a coding agent — Claude Code, Codex, or GitHub Copilot CLI — over MCP, and runs every render and narration job on your own machine. Nothing is uploaded anywhere.

npm i -g @xplainer/cli
xplainer --help

Commands

| Command | What it does | |---|---| | xplainer serve | Serves GET /healthz and the Streamable HTTP MCP endpoint at /mcp on loopback | | xplainer mcp | Serves the same tools over stdio, for an agent that spawns its MCP servers | | xplainer setup | Prepares the local render and TTS toolchain | | xplainer connect | Points Claude Code, Codex, or GitHub Copilot CLI at this daemon | | xplainer daemon | Installs and manages the always-on per-user daemon |

Run xplainer <command> --help for the flags each one takes. What is implemented today and what is still ahead is tracked in one place — docs/ROADMAP.md — rather than restated here, so this page cannot go stale against it. A command that is registered but not yet implemented says so on stderr and exits 2.

Requirements

  • Node 24. Enforced by engines, so a wrong version fails the install rather than warning.
  • Docker, for the Kokoro text-to-speech container that narration talks to.
  • A Remotion licence, depending on who you are. Remotion is free for individuals and for companies of up to three people; above that you need your own Remotion licence — see https://remotion.pro/license. @xplainer/render-core declares Remotion as a dependency of the video workspace it scaffolds and never bundles it, so your own install fetches Remotion under Remotion's terms, on your machine, in your name.

Programmatic use

createServer() and startServer() build the same Hono application the binary serves, against any RenderBackend from @xplainer/mcp-server. The exact exported surface is api/cli.api.md in the repository, which is regenerated and reviewed on every change.

Docs

Licence

Apache-2.0. See LICENSE and NOTICE, both shipped inside this package.