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-signverify

v1.0.2

Published

A package to sign and verify messages using did resolvers and JWKs

Readme

Allows for signing and verifying of content using privateJWKs from keypairs generated using ed25519 curve.

Currently supports JsonWebKey2020 using ed25519.

Supports creation and resolving of did:web and did:key based identifiers.

At the moment, this is limited to creating JSON Web Signatures in the following style

{
  content: {
      // This holds whatever body is required for the API
  },
  authorisation: {
      payload : this is the signed content
      signature : this is the signed header
  }
}

For example, you could use this to add did-based authorisation to API calls. In order to achieve this, you will need to add functionality to your consumer app to sign messages using your private key and add functionality to your APIs to verify these signatures.

Below is a simple example of using the package

import {sign, verify, DidKeyResolver, DidResolver} from "signverify"


let didResolver = new DidResolver()
let did = await DidKeyResolver.generate()

let content = "My Name is Jake"

// as the message sender, I have access to my private key so can create the authorisation object
let authorisation = await sign(content, did)

let signed_message = {
    content: content,
    authorisation: authorisation
}


// as the message verifier, I do not have access to the public key directly, so I have to resolve the on the did
let didDoc = await didResolver.resolve(did.did)
let did1public = didDoc.didDocument.verificationMethod[0].publicKeyJwk

// DIDDoc resolving is handled directly by the verify method
let verified_message_did = await verify(signed_message)