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

@kpstreams/webrtc-client

v0.1.0

Published

Browser WebRTC client for KPS: dial a server pinned by its certificate hash and open/accept unnamed byte streams. Zero native deps.

Readme

@kpstreams/webrtc-client

Browser WebRTC client for KPS (Key-Pinned Streams): dial a server pinned by its certificate hash and open/accept unnamed, reliable byte streams — plus unreliable datagrams. No CA, no domain, no signaling server. Zero native dependencies (pure WebRTC in the browser).

An address is ip:port:certhash. The client derives the ICE password from the certhash and pins the server's DTLS certificate against it, so only the holder of that exact certificate can complete the handshake.

Install

npm install @kpstreams/webrtc-client

Usage

import { dial } from '@kpstreams/webrtc-client'

const conn = await dial('203.0.113.5:41108:uEiD...')

// open a byte stream (WHATWG ReadableStream / WritableStream of Uint8Array)
const stream = await conn.openStream()
const writer = stream.writable.getWriter()
await writer.write(new TextEncoder().encode('hello'))
await writer.close()                 // half-close; peer sees EOF

for await (const chunk of stream.readable as any) { /* ... */ }

// unreliable datagrams (≤ ~1100 bytes is safe; oversized send rejects 'too-large')
await conn.sendDatagram(new Uint8Array([1, 2, 3]))
// const dg = await conn.receiveDatagram()            // next inbound datagram

await conn.close()

One-shot convenience — dial, open one stream, and tie the connection's lifetime to it:

import { openStream } from '@kpstreams/webrtc-client'
const stream = await openStream('203.0.113.5:41108:uEiD...')

API

  • dial(addr, opts?): Promise<Connection>opts: { signal? }. Timeout is via the signal: pass AbortSignal.timeout(ms) (or AbortSignal.any([sig, AbortSignal.timeout(ms)])); with no signal a ~15 s default timeout applies.
  • openStream(addr, opts?): Promise<Stream> — one-shot; closing the stream closes the connection.
  • parseAddress / formatAddress re-exported from core for convenience, plus the Connection / Stream / DialOptions types. (Identical surface to @kpstreams/quic-client — same job, different transport.)

Built on the browser's RTCPeerConnection (and crypto.subtle), so it runs in a secure context (https / localhost). A Node WebRTC client is a separate future package.

License

MIT