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

@airprompter/protocol-conformance

v0.1.0

Published

The AirPrompter agent protocol's conformance harness: every vector in protocol/vectors, run against any SDK through a JSON adapter (an ES module, or any process speaking JSON lines). The reference implementations and the schema/example runner ride along.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

airprompterairprompter

Keywords

Readme

Conformance

Two runners. run.mjs is the protocol's own gate (below). harness.mjs (S14) is the gate an SDK ships: every vector, run against any SDK through a JSON adapter — an ES module or a process speaking JSON lines — published as @airprompter/protocol-conformance with the vectors bundled:

npx airprompter-conformance --adapter ./adapter.mjs
npx airprompter-conformance --adapter-command "python3 adapter.py"

The adapter contract is ADAPTER.md; adapters/reference.mjs is the yardstick, adapters/agent-sdk.mjs the TypeScript packages, ../examples/conformance-adapter/python/adapter.py the Python SDK. A section the adapter cannot answer is skipped and reported, never passed. node --test test/harness.test.mjs is the harness's own suite (wrong answers fail by name, the pipe transport, npm pack self-containment).

npm ci && npm test here runs, against ../protocol:

  1. every schemas/*.schema.json compiles as JSON Schema 2020-12 (strict);
  2. every examples/*.json validates against its schema and every examples/refused/*.json is refused;
  3. the rules a schema cannot express hold on every example manifest and bundle — the release digest reproduces from the slots, each arm's digest reproduces from slots + overrides, countersignatures cover every arm on a countersign target, a bundle carries every referenced payload and the bytes hash to their contentHash;
  4. the reference implementations in reference.mjs pass every vector in vectors/.

npm run lint:openapi lints openapi.yaml.

node live.mjs --base-url <url> --root <root.pub.json> --api-key <key> (S12) exercises a running registry over HTTP with the same schemas and the same trust chain: the root, the edge pointer, the manifest (401 without a key, 403/404 for another agent, 304 on its ETag, verified against the root the caller pins), every referenced payload fetched and hashed, the catalogue, the heartbeat (a schema-valid answer, a lease in the future, a 400 for a field the schema does not name). airprompter dev is the target CI runs it against; Hangar and the hosted service are the same target with their own URL, root and key.

The reference implementations are the smallest correct versions of the protocol's pure functions (canonical JSON, sticky assignment, step ordering). SDKs may copy them; they must pass the same vectors either way. Manifest signature verification with real keys joins this runner with the trust-chain ticket, and each SDK's spool writer and feedback validator are exercised here once they exist. The compatibility table in the root README is generated from this run.