Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Rename to "did-jose"

See original GitHub issue

This package now contains many things related to the JOSE spec. We should modularize it to a few different (to be determined) packages.

Suggestion:

@did-jose/jws
@did-jose/jwe
@did-jose/jwt
@did-jose/jwt-vc
@did-jose/signing-*
@did-jose/encryption-*

Issue Analytics

State:
Created 2 years ago
Reactions:4
Comments:10 (8 by maintainers)

Top GitHub Comments

2reactions

peacekeepercommented, May 18, 2021

Hey, since this is a work item of the I&D WG, if you rename it then maybe you could also update the entry in the list of Work Items, and while doing that also check the work item leads that are listed there?

Perhaps we will also ask you at some point to give a general update on the work item progress during one of the weekly I&D WG calls.

0reactions

mirceaniscommented, Jul 5, 2022

The way I see it, the goals of this would be to:

allow folks to use a subset of features (if they want) to reduce their bundle sizes
allow alternative implementations of algorithms (stablelib vs noble vs elliptic vs etc…)
allow extension with other algorithms that are not covered here yet
[optional] move the did-jwt-vc library here as one of the packages

Perhaps we can start with the alternative/extension use-cases, where the [currently hardcoded] mapping of algorithms to verifiers is made configurable (see #234 as well).

There is also another mapping of algorithms to signers which probably doesn’t make much sense anymore, since the signer is expected to be provided externally anyway.

I haven’t yet gone through the JWE code to see how we can start to slice it into modules