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

@tabcat/zzzync

v6.0.0

Published

sync with peers that have gone to sleep 😴

Readme

💤ync

A libp2p protocol for handing a signed dataset to another peer that can serve it as a verifiable replica of the original publisher.

Push protocol

Protocol id /zzzync/push/1.0.0.

sequenceDiagram
  autonumber
  participant D as Dialer (publisher)
  participant H as Handler

  D->>H: open /zzzync/push/1.0.0
  D->>H: IPNS key
  D->>H: auth frame (optional; varint length, 0 = none)
  H->>D: challenge nonce
  D->>H: dialer nonce + signature
  Note over H: signature proves the dialer holds the key
  Note over H: key and auth frame checked by allow.multihash
  D->>H: signed IPNS record
  Note over H: record checked by allow.record
  H->>D: record accepted (1 byte)
  D->>H: CAR file (root matches the record)
  Note over H: every block verified to descend from the root
  Note over H: verified record handed to the app (onReceive) to pin and serve

A publisher proves it holds an IPNS key, sends a signed IPNS record, and waits for the handler to accept it before streaming a CAR of its content. The handler verifies the signature and the content, then hands the record to your application to pin and serve. The acceptance step matters: the handler is not reading the stream while it runs its checks, so a dialer that sent the CAR straight after the record would pile the whole transfer into a buffer nobody is draining.

The dialer can pass an optional auth frame (a delegation-chain CAR, for example) via dialZzzync's auth option, a function returning the frame's bytes. The handler byte-caps it (default 16KiB, override via CreateHandlerOptions.maxAuthFrameBytes) and hands it to allow.multihash, which runs only after the challenge, so an application callback never sees a key the dialer has not proven it holds.

The result is a durable, verifiable copy that stays available even while the publisher is offline.

Install

npm install @tabcat/zzzync

Docs and Usage

API reference and examples: https://tabcat.github.io/zzzync

Credits

Won a gold medal at HACKFS 2022. Additional work was funded by a Protocol Labs grant. Current work is independent.