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

@persona-claims/http

v0.2.0

Published

Reference REST transport schemas for the Claims protocol.

Readme

@persona-claims/http

Reference REST transport schemas for the Claims protocol.

This package exists only to back the reference HTTP adapters in apps/*. It is not a replacement for the role SDKs (@persona-claims/issuer, verifier, wallet, witness, gatekeeper) — those are the right dependency for embedding protocol roles into your own systems.

What it owns

  • zod schemas for every REST request/response shape
  • contentTypes namespace with the three protocol-specific MIME types
  • a small postJson helper for naïve clients

Content types

import { contentTypes } from "@persona-claims/http";

contentTypes.claims;   // "application/persona+claims"
contentTypes.request;  // "application/persona+request"
contentTypes.response; // "application/persona+response"

Schemas

Each REST endpoint has a request and response schema. The naming is short and consistent: IssueRequestSchema / IssueResponseSchema, VerifyRequestSchema / VerifyResponseSchema, ReissueRequestSchema / ReissueResponseSchema, RevocationRequestSchema / RevocationResponseSchema, and so on.

All schemas are plain zod objects, parse to fully typed values, and can be reused by clients to validate replies.

Intended consumers

  • apps/issuer
  • apps/verifier
  • apps/witness
  • apps/gatekeeper

Boundaries

  • No issuer / verifier / wallet / witness / gatekeeper logic
  • No persistence, no DNS, no signature verification
  • For an embedded role, depend on the corresponding @persona-claims/<role> package