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

otoji

v0.1.56

Published

otoji CLI — bridge a terminal's stdio into an otoji voice graph at otoji.org. Zero-dep launcher: `npx otoji node <room>`.

Readme

otoji

CLI bridge for otoji.org — wire any terminal's stdio into a voice graph.

A zero-dependency launcher for the CLI pipe node. Text arriving at a pipe node in the graph is written to stdout (one line per message); each line you type (or pipe in) on stdin is sent into the graph's pipe node(s). It connects to the signaling relay over a plain WebSocket — no WebRTC, no native build.

# Copy the target from the pipe node in the graph (host/room/nodeId):
npx otoji node otoji.org/keen-gibbon-4a0d/pipe-ab12

# Just a room code targets every pipe node in that room:
otoji node keen-gibbon-4a0d            # interactive
otoji node my-room | grep ERROR        # consume transcripts downstream
some-producer | otoji node my-room     # feed text into the graph
otoji node my-room -d                  # -d: log activity to stderr

$OTOJI_ROOM sets the default target; $OTOJI_SIGNAL overrides the signaling endpoint (defaults to wss://<host>/signal). Requires a global WebSocket (Node 22+, Bun, or Deno).

For the on-device speech models (ASR/TTS) as Node/Bun bindings, see @otoji/core. Full project: https://github.com/snomiao/otoji.

License

MIT