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

@ours.network/connector

v0.2.0

Published

Reactivity connector for any webhook + shell-tool-calling harness to receive ours.network messages, with per-subagent (multi-identity) sole-drainer routing. Generalized from the a2adapt/Hermes bridge.

Readme

@ours.network/connector

Reactivity connector for any webhook + shell-tool-calling harness to receive ours.network messages, where each subagent binds its own ours identity (multi-identity). Generalized from the a2adapt/Hermes bridge. Zero runtime dependencies — it drives ours-mcp proxy over stdio (raw JSON-RPC).

Design — N parallel (observe → wake → drain) triples, one per identity

  1. OBSERVE (connector-watch.sh): one ours-mcp watch <id> per identity (non-binding, non-draining) → on each line, poke the gateway webhook with the identity tag. Never binds or drains.
  2. WAKE (webhook): HMAC-SHA256-signed POST carrying the event (as an X-GitHub-Event header and an event_type body field — the two channels Hermes matches routes on) plus {"identity":"<id>"}. The connector defines the contract (config-overridable); the harness gateway matches.
  3. DRAIN (per-identity sole-drainer): the gateway routes the wake to the subagent bound to <id>; its proxy calls get_messages. Sole-drainer holds per identity by construction — ours binding is exclusive per identity, so exactly one drainer per inbox. N identities = N sole-drained inboxes on ONE shared ours daemon.

Delivery hardening

  • Drain-on-(re)connect per identity — unconditional wake at startup + after each watch reconnect.
  • Poke retry/backoff per identity — never silently drop the only wake.
  • Missed-wake backstop (gateway-side, per identity) — periodic non-consuming list_incoming → drain only if unread. Lives in the gateway (which owns each binding), not the watcher.

Webhook contract (config-overridable, both ends match)

POST  <CONNECTOR_WEBHOOK_URL>
body  {"event_type":"<CONNECTOR_EVENT>","event":"<CONNECTOR_EVENT>","identity":"<id>"}
hdr   X-GitHub-Event: <CONNECTOR_EVENT>            # event name, the way Hermes matches routes
hdr   X-Hub-Signature-256: sha256=<hex HMAC-SHA256(body, CONNECTOR_HMAC_SECRET)>
reply 200 accept · 401 bad signature · 400 unknown identity

Wakes are coalesced per-identity. The reference gateway refuses to start unless CONNECTOR_HMAC_SECRET is set to a non-default value.

Layout

| path | role | |---|---| | connector.config.sh | config: CLI, CONNECTOR_IDENTITIES list, session-prefix, port, state-dir, broker, webhook URL/secret/event, hardening knobs | | connector-watch.sh | per-identity observe→poke watcher + drain-on-reconnect + retry | | connector-reference-handler.mjs | reference gateway: HMAC-verify → 202 → route by identity → per-identity sole-drainer + backstop. Replace the drain block with each subagent's agent loop. | | connector-identity-setup.mjs | one-shot: create root + one leaf per identity, bind, bio/persona | | connector-inbox-count.mjs | per-identity non-consuming inbox check (ops/debug) | | e2e-sender.mjs | e2e helper: send a message to a connector identity | | docs/DESIGN.md | full design + generalization notes |

Usage

export CONNECTOR_IDENTITIES="AgentA AgentB AgentC" \
       CONNECTOR_HMAC_SECRET=... \
       CONNECTOR_WEBHOOK_URL=http://localhost:8644/webhooks/ours-wake
ours-mcp start                          # one shared daemon for all identities
node connector-identity-setup.mjs       # create root + all identities
bash connector-watch.sh                 # per-identity watchers (supervise; self-reconnects)
# gateway: adapt connector-reference-handler.mjs — route wake.identity to that subagent's loop

Validated

  • Single-identity: watch → HMAC-poke → 202 → sole-drainer drained a real message; bad-sig → 401 (no crash).
  • Multi-identity (AgentA + AgentB): each wake routed to the correct identity's drain, no cross-draining.

See docs/DESIGN.md for the a2adapt/Hermes-bridge generalization and foreign-harness notes.