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 🙏

© 2025 – Pkg Stats / Ryan Hefner

did-jwks

v1.0.0

Published

A DID method that enables JWKS endpoints to be used as DID identifiers

Readme

did-jwks

Core implementation of the did:jwks method that enables OAuth2/OIDC JWKS endpoints to be used as DID identifiers.

Installation

npm install did-jwks

In most cases, you will want to use the []jwks-did-resolver](../jwks-did-resolver) packages with the did-resolver package.

Usage

import { fetchJwksDidDocument } from "did-jwks"

const didDocument = await fetchJwksDidDocument("did:jwks:accounts.google.com")
console.log(didDocument)

CLI

npx did-jwks did:jwks:accounts.google.com

API

fetchJwksDidDocument(did: string): Promise<DidDocument>

Fetches a DID Document for a did:jwks identifier.

import { fetchJwksDidDocument } from "did-jwks"

const didDocument = await fetchJwksDidDocument("did:jwks:example.com")

console.log(didDocument)

How It Works

  1. Parse DID: Extracts domain and optional path from the DID
  2. JWKS Discovery: Attempts to fetch JWKS from:
    • Direct: https://domain/.well-known/jwks.json
    • OAuth2 Discovery: https://domain/.well-known/openid-configuration
  3. Transform: Converts JWKS keys to DID verification methods
  4. Generate: Creates a standard DID document

Examples

Google OAuth2

const result = await fetchJwksDidDocument("did:jwks:accounts.google.com")
// Resolves Google's JWKS for OAuth2 token verification

GitHub Actions

const result = await fetchJwksDidDocument(
  "did:jwks:token.actions.githubusercontent.com"
)
// Resolves GitHub's JWKS for Actions token verification

Custom Domain with Path

const result = await fetchJwksDidDocument(
  "did:jwks:auth.example.com:tenant:123"
)
// Resolves to https://auth.example.com/tenant/123/.well-known/jwks.json

License (MIT)

Copyright (c) 2025 Catena Labs, Inc. See LICENSE for details.