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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@japikey/authenticate

v0.4.0

Published

Library to authenticate an API key, in the browser or backend

Downloads

77

Readme

@japikey/authenticate

This package is used whenever you have an API key, and you want to check to see if it's valid and the claims stored within it

This package understands api keys created by the @japikey/japikey library. Since these keys use public/private key cryptography, it depends on the caller providing the public key. This can either be done manually, or via a URL such as .well-known/jwks.json

This package is part of the @japikey constellation of packages. See @japikey/japikey for more details

Usage

Given a known issuer (the server that generated your api key), you can set the issuer to that URL Then, if your server is implementing the JWKS scheme of this repository, you can use createGetJWKS to get the correct public key for the token.

The authenticate method takes the public key, and uses jose.jwtVerify() to validate the api key

import { createGetJWKS, authenticate } from '@japikey/authenticate';
const issuer = new URL('https://example.com');
const getJWKS = createGetJWKS(issuer);
await authenticate(my_auth_token, { getJWKS, baseIssuer });

The authenticate method will throw a JapikeyError upon failure. See @japikey/shared for more details about error handling.

In addition, you can also use the shouldAuthenticate method to determine if the access token appears to be a japikey (based on its unverified claims)

import { shouldAuthenticate } from '@japikey/authenticate';
const issuer = new URL('https://example.com');
const isJapikey = shouldAuthenticate(my_auth_token, issuer);