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

@onderling/agent-registry

v0.1.0

Published

Canonical agent registry — the user's agents listed in one pod resource. Implements core's ActorResolver. Etag-based optimistic concurrency. Standardisation Phase 52.10.

Readme

@onderling/agent-registry

The user's agents listed in one canonical pod resource. Implements core's ActorResolver interface so PolicyEngine + CapabilityToken.verify can bridge between identifier shapes (pubKey / webid / agentUri / agentId / deviceId).

Standardisation Phase 52.10. See Project Files/Substrates/substrates-v2-coding-plan-2026-05-11.md §52.10.


npm install @onderling/agent-registry

Quick start

import { createPseudoPod, createMemoryBackend } from '@onderling/pseudo-pod';
import { createAgentRegistry, makeActorResolver } from '@onderling/agent-registry';

const pseudoPod = createPseudoPod({ /* … */ });
const registry  = createAgentRegistry({
  pseudoPod,
  anchorPodUri: 'https://anne.pod',   // or omit + supply deviceId for no-pod
});

await registry.register({
  agentId:      'laptop-anne',
  pubKey:       '<base64>',
  webid:        'https://anne.pod/profile#me',
  agentUri:     'https://anne.pod/profile#me/agent/laptop',
  role:         'device',
  name:         'Anne (laptop)',
  deviceId:     'laptop-anne',
  capabilities: ['stoop', 'tasks'],
});

await registry.lookup('<base64>');                  // by pubKey
await registry.lookup('https://anne.pod/profile#me'); // by webid

// Bridge into core's ActorResolver-shaped consumers.
const resolver = makeActorResolver(registry);
agent.policyEngine.setActorResolver(resolver);

Wire shape

Lives at <anchor-pod>/private/agent-registry (or pseudo-pod://<deviceId>/private/agent-registry for no-pod users):

{
  "v": 1,
  "agents": [
    {
      "agentId":   "laptop-anne",
      "pubKey":    "<base64>",
      "webid":     "https://anne.pod/profile#me",
      "agentUri":  "https://anne.pod/profile#me/agent/laptop",
      "role":      "device",
      "name":      "Anne (laptop)",
      "deviceId":  "laptop-anne",
      "capabilities": ["stoop", "tasks"],
      "signedAt":  "2026-05-11T10:00:00Z",
      "revokedAt": null
    }
  ],
  "updatedAt": "2026-05-11T10:00:00Z"
}

Forward-additive: extra fields on agents tolerated; renames require a new entry path.


API

createAgentRegistry({ pseudoPod, anchorPodUri?, deviceId?, resourceUri?, maxRetries?, onPersistentConflict?, now? })

await registry.register(entry)              // create or update by agentId
await registry.lookup(identifier)            // pubKey / webid / agentUri / agentId / deviceId
await registry.revoke(identifier)            // sets revokedAt
await registry.updateCapabilities(id, caps)  // replace caps array
await registry.list()                        // full agent list (frozen)
await registry.reload()                      // re-read from pod

registry.resourceUri                          // computed URI
makeActorResolver(registry) → ActorResolver
  // implements core's ActorResolver interface (resolve / register / revoke)
  // resolve(identifier) → { pubKey, webid, agentUri, role, capabilities, revokedAt } | null

Concurrency

Each mutation reads the current resource (with its etag), applies the change, and writes back with If-Match: <etag>. On CONFLICT (412-shaped error from the pseudo-pod's underlying store) we backoff + retry (default 3 attempts, exponential 10/50/200 ms). After exhausting retries, the substrate surfaces a PERSISTENT_CONFLICT error and fires the caller-supplied onPersistentConflict callback — typical UX: prompt the user to reload.

Note: pseudo-pod V0/V1 doesn't yet enforce CAS itself. The substrate-level retry helper is wired so that when a pseudo-pod backend gains etag-aware writes (Phase 52.8.x conflict-resolution work), the agent-registry substrate gets concurrency for free.


What V0 deliberately does not do

  • Cross-user resolution. This registry holds ONE user's agents. Apps that need to bridge across users use the existing @onderling/identity-resolver MemberMap on top — the agent-registry-backed adapter ships in Phase 52.11.
  • Signature verification. The signedAt field exists for audit-trail consumers; the substrate does not verify the signature on read. Real-pod ACPs gate write access.
  • Bulk migrate. No batch register / revoke API. Apps loop over individual calls; each enjoys the per-entry CAS retry.
  • WebID profile patching. Pointer predicates on the user's WebID profile (dec:agent-registry-uri) are wired by @onderling/pod-onboarding (Phase 52.5).

Status

0.x — pre-1.0; the API may move between minor versions. Versioned with changesets. Source: github.com/Onderling/basis (packages/agent-registry).