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

@volter/teams

v0.2.3

Published

Volter Teams, the neutral team plane: machine identity and daemon core, the local door and server link, admission from machine grants, product doors, and the Teams server's neutral routes (company RFC 0008).

Readme

@volter/teams

Volter Teams, the neutral team plane (company RFC 0008): what any product needs to be reached by a team, with no harness in it.

  • The machine daemon's core (machine-core.mjs): this OS user's machine identity and hash-chained account log, the owner-only local door, one outbound link to a Teams server with every stream admitted from the machine's own synced grants, and product doors. A product builds on MachineCore and registers its own doors by stream name; the harness does (@volter/supercode-teams, machine.mjs).
  • Products behind the daemon (products.mjs): a product serving its own kind of target writes a receipt; the daemon admits the caller, both sides prove the receipt's token without sending it, and messages are relayed.
  • Admission (admission.mjs): grants of capabilities on targets, <kind>:* wildcards, * for operate and view only.
  • The Teams server's neutral routes (server/): identity and sign-in, teams, members, groups, credentials, invitations, machines, enrollment and machine grants, the machine link, and the migration chain. The harness's routes attach through api.harnessRoutes.

This package is private: nothing is published while nothing is open-sourced.

Public Node clients are @volter/teams/http-client (TeamsClient), @volter/teams/event-client (selected-context event client), and @volter/teams/machine-door (an admitted local/remote machine channel). Context credentials remain inside the custody adapter; consumers use its public client.