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-pairing

v0.1.3

Published

ARP pairing protocol — create, deliver, countersign, and verify Connection Tokens.

Vulnerabilities

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

Links

Git

Maintainers

kybernesiskybernesis

Keywords

Readme

@kybernesis/arp-pairing

Pairing protocol implementation — creates, verifies, and countersigns Connection Tokens.

Flow

  1. Issuer side. createPairingProposal compiles the chosen scope bundle into Cedar policies, then signs the canonical bytes with the issuer's principal key. Output: a PairingProposal.
  2. Delivery. buildInvitationUrl base64url-encodes the proposal JSON into a QR code or deep link (https://samantha.agent/pair?invitation=…).
  3. Audience side. parseInvitationUrl decodes it. After rendering the consent UI, countersignProposal verifies the audience's local recompile still matches the issuer's policies, signs, and projects out a ConnectionToken ready for the runtime.
  4. Either side. verifyConnectionToken (or verifyPairingProposal) takes a DidResolver and re-validates both signatures + expiry.

Canonicalization

All signatures are computed over the JCS (RFC 8785) serialization of the nine connection-payload fields: connection_id, issuer, subject, audience, purpose, cedar_policies, obligations, scope_catalog_version, expires. sigs itself is never included in the hashed bytes. The same payload shape is used whether you start from a proposal or a token, so a proposal's signatures carry verbatim into its ConnectionToken.