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

@sealkeeper/schema

v0.4.3

Published

Zod schemas, event taxonomy and signing helpers for SealKeeper.

Vulnerabilities

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

Links

Git

Maintainers

carelmeyercarelmeyer

Keywords

Readme

@sealkeeper/schema

Shared schemas and helpers for SealKeeper, the reputation layer for AI agents.

  • @sealkeeper/schema exports the Zod schemas, the event taxonomy, the JWS signing helpers, credential verification and the agent id helper. No database dependency. The sealkeeper CLI bundles this entrypoint.
  • @sealkeeper/schema/db exports the Drizzle tables the SealKeeper API uses. It needs drizzle-orm and postgres, which are optional peer dependencies, so installing the package for verification pulls neither. Install both yourself to use this entrypoint.
npm install @sealkeeper/schema

Issuer and keys path

From 0.4.0 a SEAL carries iss sealkeeper.run (CREDENTIAL_ISSUER) and the keys document lives at /.well-known/seal.json (WELL_KNOWN_PATH, full URL WELL_KNOWN_URL). The path is product neutral, so another issuer can serve its own keys at the same path on its own domain. The old path /.well-known/vouched.json (LEGACY_WELL_KNOWN_PATH) is served beside it for one release. SEALs issued as vouched.run before the cutover stay valid until they expire, at most 24 hours. acceptedIssuer(iss, nowSeconds) accepts sealkeeper.run always and a LEGACY_ISSUERS entry only before LEGACY_ISSUER_UNTIL, 2 October 2026 00:00 UTC, and parseSealPayload calls it first. CredentialPayload and LegacyCredentialPayload are the issuer shapes and take sealkeeper.run only, so an issuer never writes or re-serves a legacy issuer. Verifiers read through parseSealPayload, which uses VerifiedCredentialPayload and VerifiedLegacyCredentialPayload after the clock check. Cards carry the SEAL under https://sealkeeper.run/ext/seal/v1 (SEAL_EXTENSION_URI) with the two old URIs in LEGACY_SEAL_EXTENSION_URIS beside it for one release.

Licensed under Apache-2.0. See LICENSE and NOTICE.