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

@network-harness/protocol-router

v0.2.0

Published

Part of the network harness: @network-harness/protocol-router.

Readme

@network-harness/protocol-router

A human types one thing, and something has to decide which protocol that is.

The only protocol here that talks to no peer. It reads what the network is offering -- the skills board, the query board, and what this human holds -- asks its own agent which of those the text is asking for, and writes the answer down.

Dispatching is deliberately not its job. An interface reads the decision, starts the thing, and says what it started. A protocol that reached into another protocol to start work would be deciding on that protocol's behalf, with its own caller, and none of the caller-derived accounting the harness is built on would mean anything.

What it can route to is not a list in this file. The choices are the intents the protocols installed on this node declare, read back from what the host advertises, so a protocol somebody adds afterwards is routable the moment it is installed, and one that is removed stops being offered -- without this protocol knowing anything about either.

The board is the part worth being careful about. Its rows come from a directory: not this node, not a peer this node chose, so a name or a description is text of unknown origin. It travels as the run's context, which the loop delimits and labels as data, and anything in it that could close a delimiter is neutralized first -- otherwise a hostile row would not so much inject a prompt as break every routing run this node ever does. The model's answer is then re-validated against the live board: a skill that is not on it cannot be picked.

| | | | --------- | ----------------------------------------------------------------------------------------------------------------- | | routes | POST /prompts, GET /prompts, GET /board, POST /prompts/:prompt/dispatched, POST /prompts/:prompt/failed | | payloads | none -- nothing crosses the wire | | schedules | sweep every 60s, for a decision nothing ever dispatched | | needs | any source, to say what this human holds; no operations, no tools | | intents | none: it is the thing that routes, not a thing routed to |