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

did-nostr

v0.0.2

Published

did:nostr resolver — offline, HTTP (.well-known) and relay resolution, with a DIF did-resolver driver. Conforms to did:nostr 0.0.12.

Downloads

183

Readme

did-nostr

A did:nostr resolver — offline, HTTP (.well-known), and relay resolution, with a DIF did-resolver driver. Conforms to did:nostr 0.0.12.

The spec lives at nostrcg/did-nostr. This package is the resolver.

Install

npm install did-nostr
# optional, for the DIF driver:
npm install did-resolver

ESM only. Node ≥ 20 (relay resolution needs a global WebSocket — Node ≥ 22 or a browser).

Library

import { resolve, buildDidDocument } from 'did-nostr'

// Full strategy: HTTP .well-known (fast) -> relay (enhanced) -> offline (minimal)
const { didDocument } = await resolve('did:nostr:124c0f…fdd2')

// Pure, offline, no network — minimal document from the key alone:
const minimal = buildDidDocument('124c0f…fdd2')

DIF did-resolver driver

import { Resolver } from 'did-resolver'
import { getResolver } from 'did-nostr'

const resolver = new Resolver(getResolver({ gateways: ['https://nostr.social'] }))
const result = await resolver.resolve('did:nostr:124c0f…fdd2')
// -> { didResolutionMetadata, didDocument, didDocumentMetadata }

CLI

did-nostr <did|pubkey> [options]

  --offline           minimal document from the key alone (no network)
  --http              HTTP .well-known only (fast)
  --relay             relays only (enhanced)
  --gateway <url>     HTTP gateway to try (repeatable)
  --relay-url <url>   relay to query (repeatable)
  --json              print the full DID resolution result
  -h, --help

Resolution strategy

  1. Offline / minimal — DID document from the public key alone, no network.
  2. HTTP (.well-known)GET <gateway>/.well-known/did/nostr/<pubkey>.json (fast path).
  3. Relay / enhanced — query relays for kind 0 (profile), 3 (follows), 10002 (relays) and build the document locally.

resolve() in auto mode tries HTTP first, falls back to relay, then to offline-minimal.

Conformance

Key transformation, decoding, the error taxonomy, and minimal document generation are gated against the did:nostr conformance vectors (npm test). This is an independent implementation of the same vectors that Beacon passes.

License

MIT