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

@simbachain/simba-chain-vc

v0.3.10

Published

Utilities for signing VCs and creating VPs

Downloads

424

Readme

simba-chain-vc

This library provides utilities for working with DID Documents, Verifiable Credentials (VCs) and Presentations (VPs).

Currently it is focussed on the minimal client side capabilities of:

  1. Creating SIMBA VPs given VCs that have been provided by the server where a local public key/ethereum address is mapped to the DID subject of that VC.
  2. Finding the verification method (aka DID Document key reference) mapped to a public key or address.
  3. Determining issuer and subject DIDs given a VC.
  4. Creating a new private key from which public key and address can be derived.
  5. Signing arbitrary data outside of the ethereum use case.
  6. Creating JWK serializations of public and private keys.
  7. Creating a multicodec serialization of public keys.

Note that (almost) all functionality is currently based on ERC 191 capabilities that are used by the ERC191 crypto suite defined by SIMBA. Therefore secp256k1 keys are assumed and when we say public key we usually mean ethereum address, as the address is the public part of the key pair as far as blockchain and the SIMBA ERC191 suites is concerned.

The non-ethereum signing (#5 above) is used to sign DPoP headers. These signatures are verified by the public key NOT an ethereum address. For Secp256k1, this signing uses deterministic signing (no salt/nonce) and returns a 64 byte signature over 32 bytes of data. It is assumed that any data that is not 32 bytes needs to be hashed and the hashing alg is SHA256. An optional nonce can be added to this signing which is simply appended to the data before signing.

Multicodec public keys (not addresses) can be used as verification methods in DID documents.