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

@utterance/core

v0.0.5

Published

Client-side semantic endpointing. Know when they're done talking.

Readme


The Problem

Every voice app faces the same annoying problem: it can't tell when you're done talking.

You pause to think, and it cuts you off. You take a breath, and it responds too soon. You want to interrupt, and it keeps going.

The current solutions either:

  • Detect silence (Silero VAD, ricky0123/vad): They know when sound stops, but they can't tell if you're thinking or finished.
  • Use server-side AI (OpenAI Realtime, AssemblyAI): They are smart, but they add delay, costs, and privacy issues.

Utterance is different. It uses a lightweight ML model entirely on the client side. It recognizes the difference between a thinking pause and a completed turn. No cloud. No delay. No per-minute fees.

Quick Start

npm install @utterance/core
import { Utterance } from "@utterance/core";

const detector = new Utterance();

detector.on("turnEnd", (result) => {
  console.log("User is done speaking", result.confidence);
});

detector.on("pause", (result) => {
  console.log("User is thinking...", result.duration);
});

detector.on("interrupt", () => {
  console.log("User wants to speak — stop AI response");
});

await detector.start();

See the full documentation for detailed usage, API reference, and integration examples.

Comparison

| Feature | Silero VAD | ricky0123/vad | Picovoice Cobra | OpenAI Realtime | Utterance | | --- | --- | --- | --- | --- | --- | | Detects speech vs. silence | ✅ | ✅ | ✅ | ✅ | ✅ | | Semantic pause detection | ❌ | ❌ | ❌ | ✅ | ✅ | | Interrupt detection | ❌ | ❌ | ❌ | ✅ | ✅ | | Runs client-side | ✅ | ✅ | ✅ | ❌ | ✅ | | No API costs | ✅ | ✅ | ❌ | ❌ | ✅ | | Privacy (audio stays local) | ✅ | ✅ | ✅ | ❌ | ✅ |

Contributing

We're building Utterance in the open, and contributions are welcome.

git clone https://github.com/nizh0/Utterance.git
cd Utterance
npm install
npm start

See the contributing guide for development workflow, project structure, and areas where we need help.

Community

License

MIT © Utterance