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

@orbitalfoundation/streams

v0.1.0

Published

Room-based conversation over an orbital filespace: a durable per-area message log, gated by filespace policy, exposed as a single listener on the orbital bus.

Readme

@orbitalfoundation/streams

Room-based conversation over an orbital filespace — a durable per-area message log, exposed as a single listener on the orbital bus.

A chat room is not a new concept here: it is a filespace node whose message log this service owns. Permissions are not reinvented — they are filespace's, consulted live:

  • tail (read history): you may read a room's log iff you may read the node — privacy and ancestor-chain inheritance included. Hidden rooms have no history, as far as you can tell.
  • post: filespace's reserved post verb — guests may post in public rooms, members anywhere they belong. This is the verb the policy table held open for exactly this layer.

One reserved bus key, mirroring filespace:

{ streams: { query:   { op: 'tail', slug, after?, limit? } } }
{ streams: { command: { op: 'post', slug, body, label?, principal, auth } } }
{ streams: { changed: { op: 'post', slug, message } } }   // announced after a post

Authentication reuses filespace's signed-envelope guard verbatim. A message is { seq, slug, author, label, body, at }seq is a server-assigned per-room sequence (order and backfill), author is the signer's public key, label is a display name.

Messages are not entities

Different churn, different shape, different store. The message store contract is three methods (append, tail, rooms) with two adapters: memory, and fileJSONL, because a conversation is an append-only log (one line per message; replayed at boot; no rewrite-the-world per post).

Presence is deliberately not here

The other half of "streams" — who's in the room, cursors, typing, live markers — is ephemeral, per-connection, latest-wins state. It belongs to the transport (@orbitalfoundation/server keeps it in memory against socket.io rooms), never to the bus or a store. The coarse-unit principle: a wiggle is not a bus event.

Use

import { createBus } from '@orbitalfoundation/bus';
import { attach as filespace, makeFileStore } from '@orbitalfoundation/filespace';
import { attach as streams, makeFileMessages } from '@orbitalfoundation/streams';

const bus = createBus();
filespace(bus, { store: makeFileStore('.filespace/nodes.json'), authenticate: true }); // first
streams(bus, { messages: makeFileMessages('.filespace/messages.jsonl'), authenticate: true });

await bus.resolve({ streams: { command: signAction(macy, 'post', { slug: '/lounge', body: 'hi' }) } });
await bus.resolve({ streams: { query: { op: 'tail', slug: '/lounge' } } });
npm test   # store contract, policy gating end-to-end, privacy, announce, pagination

Later, deliberately

Edit/delete/reactions, msg:chunk streaming deltas (agent output), search over logs, per-room retention.