Perhaps though, there is a spelling error in runkit’s backend which is causing this error and making this package impossible to locate, given the proximity of the ‘a’ key to the ‘s’ key on a keyboard.
As was mentioned in the prior comment, jwa is a dependency. As for why it wasn’t available, it’s hard to say. It says there was an error, but the error itself was dropped from our records. The package was published some 3 years ago, could have been a bug on our end or something like npm just timing out at the time.
Regardless, I’ve reprocessed the package and it’s now available, which should fix jwt for you.