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

@weaveworm/core

v0.1.0

Published

Framework-agnostic state machines and adapter contracts for AI-native UI patterns.

Readme

@weaveworm/core

Framework-agnostic state machines and adapter contracts for AI-native UI patterns — the headless layer of weaveworm.

Zero runtime dependencies. Patterns speak only a normalized StreamEvent vocabulary (text-delta, reasoning-delta, tool-call, source, error, finish); adapters map any backend into them. That seam is what breaks SDK lock-in: swap the adapter, keep the UI.

import { createStreamMachine } from "@weaveworm/core";
import { createRawSSEAdapter } from "@weaveworm/core/adapters/raw-sse";

const adapter = createRawSSEAdapter({ url: "/api/chat" });

Adapters

| Import | Backend | | --- | --- | | @weaveworm/core/adapters/raw-sse | Plain Server-Sent Events, no SDK | | @weaveworm/core/adapters/ai-sdk | Vercel AI SDK | | @weaveworm/core/adapters/anthropic | @anthropic-ai/sdk | | @weaveworm/core/adapters/mock | Backend-free, for demos and tests |

All adapters are structurally typed, so importing one never pulls its SDK into your bundle.

Bindings

The logic lives here in portable TypeScript, so a binding for another framework is a bounded contribution.

Canon

Each pattern ships with codified best practices — the why, not just the code. See the weaveworm canon.

MIT © Shan Nadige