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

@vbel/adapter-identity-static

v0.1.0

Published

IdentityResolver over a static, explicitly-configured trust registry. The trust root is the file itself — see src/static-registry.ts.

Readme

@vbel/adapter-identity-static

An IdentityResolver over a list the verifier chooses to trust. The trust root is the list itself, so where it comes from is a decision for whoever runs the check.

pnpm add @vbel/adapter-identity-static
import { StaticIdentityRegistry } from "@vbel/adapter-identity-static";

// `raw` is untrusted JSON, such as a file on disk or a network response. It is validated before use.
const resolver = StaticIdentityRegistry.fromJSON(raw);
const attestation = await resolver.resolve("urn:example:org:supplier", event.envelope.issuedAt);

An issuer can hold several attestations with non-overlapping windows, which is how key rotation is expressed: an old event keeps resolving to the key that was in force when it was signed.

A resolver backed by a directory, ENS text records or a certificate chain satisfies the same interface, so events verified against this one stay verifiable against those without re-signing anything.

Part of VBEL

Signed, hash-chained records that anyone can check for changes, with optional anchoring on a public chain. The repository readme says what that does and does not prove.

Apache-2.0.