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

@servanda/adapters

v0.4.0-pre

Published

Servanda verification adapters: read-only, offline observers that produce the §4.4 evidence bundle whose hash an owner cites when closing an edge

Readme

@servanda/adapters

Verification — the mechanism §4.4 and M-8 presupposed and nothing implemented.

VerificationAdapter: (commitment, context) → EvidenceBundle | NotVerifiable

Why this exists

Two sentences in the spec assume a verification adapter:

  • §4.4 — an on-evidence closure is "a closed assertion by the owner with non-null evidence_hash (hash of the verification adapter's evidence bundle)".
  • M-8 — "Unverifiable edges (no adapter, or invalid collective) MUST NOT auto-escalate."

Before this package, evidence_hash was an opaque hash nobody produced and "unverifiable" had no mechanism behind it. This is the part that decides whether a promise was actually kept.

What an adapter may and may not do

An adapter observes and reports. It never asserts, never signs, never closes an edge. Closure is the owner's signed act (§4.4), and M-13 keeps automation out of the party role — an adapter that could close an edge would be an agent acting as a party rather than under one.

Bundles hash reproducibly: sha256(JCS(bundle)) is exactly the evidence_hash an assertion carries, and the same observation yields the same hash on any machine.

Registry, hardcoded and small like the executor registry: ci, git, file. Each declares what it can observe and refuses everything else.

NotVerifiable is a result, not an error

An edge no adapter can speak to is unverifiable, and M-8 then forbids auto-escalation. That path is deliberately the easy one: a caller that ignores the distinction gets the safe behaviour, a null hash and an edge that stays open, rather than a silent close.

The M-8 tests carry their own control — an overdue, verifiable on-evidence edge does escalate — so "unverifiable never escalates" cannot pass merely because nothing ever escalates.

Collective edges (§4.7, M-9)

A collective edge whose fulfillment neither covers the work through children nor names a coordinator is unverifiable, and the adapter layer says so before observing anything. Tested both ways: a covering decomposition or a named coordinator makes it verifiable again.