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

@kybernesis/arp-runtime

v0.3.2

Published

ARP runtime — Hono HTTP server, PDP pipeline, connection registry + audit orchestration, per-connection memory partitioning.

Downloads

514

Readme

@kybernesis/arp-runtime

The reference ARP agent runtime. Hono HTTP server, Cedar PDP, connection registry, hash-chained audit log, DIDComm v2 signed messaging, and per- connection memory partitioning — wired together behind a single Runtime interface.

Endpoints

| Path | Purpose | | -------------------------------- | ----------------------------------------- | | GET /health | Liveness probe + version/uptime | | GET /.well-known/did.json | W3C DID Document | | GET /.well-known/agent-card.json | Agent Card | | GET /.well-known/arp.json | Version + capability advertisement | | GET /.well-known/revocations.json | Local list, or proxied to owner URL | | POST /didcomm | DIDComm v2 signed envelope ingest | | POST /pair | Stubbed (501) — implemented in Phase 4 |

Request pipeline (POST /didcomm)

decrypt+verify signature (via @kybernesis/arp-transport)
  → load Connection Token from registry
  → verify not suspended / revoked
  → PDP.evaluate (@kybernesis/arp-pdp)
  → if allow → dispatch(handler)
  → audit.append (@kybernesis/arp-audit)
  → transport.send reply

Deny paths audit and return an error envelope; revocation audits as reason: "revoked" and short-circuits the pipeline.

Use

import { createRuntime } from '@kybernesis/arp-runtime';
import { createResolver } from '@kybernesis/arp-resolver';
import { createFileKeyStore } from '@kybernesis/arp-transport';
import schemaJson from '@kybernesis/arp-spec/cedar-schema.json' with { type: 'json' };

const runtime = await createRuntime({
  config: { did: 'did:web:samantha.agent', /* ... */ },
  keyStore: createFileKeyStore({ did, path: '/var/lib/arp/agent.key' }),
  resolver: createResolver(),
  cedarSchemaJson: JSON.stringify(schemaJson),
  registryPath: '/var/lib/arp/registry.sqlite',
  auditDir: '/var/lib/arp/audit',
  mailboxPath: '/var/lib/arp/mailbox.sqlite',
  dispatch: async ({ message, memory }) => {
    const prior = memory.get('last_seen');
    memory.set('last_seen', Date.now());
    return { reply: { prior } };
  },
});

await runtime.start(4401);

Per-connection memory

runtime.memory is an in-memory Map-of-Maps keyed by connection_id. The dispatch handler gets a pre-bound accessor:

dispatch: async ({ memory }) => {
  memory.set('knowledge', { foo: 'bar' }); // scoped to the connection
  const v = memory.get('knowledge');
}

Reads are strictly partitioned — connection_A.get(k) never returns a value written under connection_B. See docs/ARP-phase-2-runtime-core.md §4 Task 9.

Shutdown

process.on('SIGTERM', async () => {
  await runtime.stop();
});

stop() drains the transport, closes SQLite, and releases the HTTP port.