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

@kashscript/muffler

v0.1.0

Published

The Data Protocol — a transport-agnostic, did:kash-bound atproto-style PDS client + firehose indexer with CID content-addressing, an injectable Refiner (lexicon validation via @kashscript/lexicons), and pluggable record sinks (in-memory + Supabase adapter

Readme

@kashscript/muffler — the Data Protocol (PDS + firehose)

Portable hosting is free. Apache-2.0. Where record hosting/sync is the concern, ventures consume Muffler and never reach beneath it.

Built in phase M3 of the protocol Manifestation (ADR-0016). An atproto-style PDS + firehose: a transport-agnostic client writes did:kash-bound repos, a firehose indexer projects them into read models, records are content-addressed (CIDv1) and validated through an injectable Refiner. The generic machinery is derived from the @indus/muffler venture seed; the venture-specific lexicons, refine rules, rm_* projections, and Supabase schema stay venture-side. Full contract: specs/muffler.md.

What's inside

  • clientMufflerClient(transport, did, refiner?): put/deleteRecord/uploadBlob/listRecords over a transport-agnostic XrpcTransport seam (+ tid() sortable rkeys). Writes to a handled collection are refined (validated + JCS-canonical) before they leave the process.
  • indexerMufflerIndexer: subscribes a FirehoseTransport, refines each record, and pushes idempotent upserts/removes into a RecordSink keyed by (did, collection, rkey). Account deactivation purges the whole repo — the decentralization guarantee, operational. Cursor-persistent, per-message failures isolated (an invalid record is dropped, not fatal).
  • refine — the Refiner seam (handles + refine → validate · canonicalize · content-address). A venture supplies its own; createLexiconRefiner is the reference, backed by @kashscript/lexicons (validateBody).
  • cidcidForBytes (CIDv1, raw codec, sha2-256 over the JCS bytes) — the change-detection key.
  • identitymintOrgIdentity + createOrgBindingRecord/verifyOrgBindingRecord: bind a sovereign did:kash to the atproto repo it publishes to, verifiable with no server round-trip.
  • sinksMemoryRecordSink (in the barrel) and SupabaseRecordSink (behind the @kashscript/muffler/sink-supabase subpath, @supabase/supabase-js peer-dep) whose rm_* projections are injected as config.

The seam

The indexer + client depend only on the Refiner interface — never a concrete schema. A venture keeps its lexicons + refine rules + read-model projections and injects them:

import { MufflerIndexer, MemoryRecordSink, createLexiconRefiner } from "@kashscript/muffler";

const refiner = createLexiconRefiner({
  registry,                                     // a @kashscript/lexicons LexiconRegistry
  collectionToLexiconId: (c) => `${c}@1.0.0`,   // NSID -> lexicon id
});
await new MufflerIndexer({ firehose, sink: new MemoryRecordSink(), refiner }).run();

A dev-grade reference host that serves repos + emits a firehose ships as @kashscript/muffler-pds.

Status

0.x — the API stays 0.x until the venture consumer (@indus/muffler) thins onto the published package and its indexer test stays green (consumer-as-acceptance, ADR-0016). Depends on @kashscript/identity-core + @kashscript/lexicons.

Licensed Apache-2.0 — see LICENSE.