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

@red-isbe/did-isbe-resolver

v2.0.1

Published

TypeScript/ESM library to resolve `did:isbe` DIDs through the ISBE public registry API.

Readme

DID ISBE Resolver

TypeScript/ESM library to resolve did:isbe DIDs through the ISBE public registry API.

Build requirements

  • Node.js 18+
  • npm
npm install
npm run build

Usage

ResolverConfig

This class lets you define one or more DID Registry API instances. Each key is the model deploy/network segment used in the DID (the third segment in did:isbe:<modelDeploy>:<id>), and each value contains the base API URL for that deploy.

Structure:

type ResolverConfig = Record<string, { url: string }>;

Example with multiple registries:

const resolverConfig: ResolverConfig = {
  "uc-dev": {
    url: "https://identity-did-api.dev.cloud-w.envs.redisbe.com/api/v1",
  },
  "uc-pre": {
    url: "https://identity-did-api.pre.cloud-w.envs.redisbe.com/api/v1",
  },
};

Example

import { getResolver } from "./index.js";
import process from "process";
import type { ResolverConfig } from "./src/types.js";
import { Resolver } from "did-resolver";

const DEV_API_URL =
  "https://identity-did-api.dev.cloud-w.envs.redisbe.com/api/v1";
const DID_URL = "did:isbe:uc-dev:z1VDuuYvwpXRNoi9HG9gYga1nPfG";

async function main() {
  const resolverConfig: ResolverConfig = {
    "uc-dev": {
      url: DEV_API_URL,
    },
  };
  const isbeResolver = getResolver(resolverConfig);
  const didResolver = new Resolver(isbeResolver);

  const didDocument = await didResolver.resolve(DID_URL);

  console.dir(didDocument, { depth: null, colors: true });
}

main().catch((err) => {
  console.error(" Error al resolver:", err);
  process.exit(1);
});