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

@hlao-adapter/microsoft-entra-id

v0.1.0

Published

OIDC ID-token verification against Microsoft Entra ID (Azure AD) JWKs. Reference implementation of an HLAO verifyActor source for backends that receive an Entra ID token from a client.

Readme

@hlao-adapter/microsoft-entra-id

OIDC ID-token verification against Microsoft Entra ID (formerly Azure Active Directory). Reference implementation of an HLAO verifyActor source: a deployment uses verifyToken to authenticate the caller and verifyActor in the runner's CreateRunnerDeps to gate approvals.

What this adapter does

Verifies the JWT signature of an Entra ID token against the tenant's public JWKs, checks audience (aud), issuer (iss), expiry, and (optionally) an explicit allowlist of principals. Returns { actorId, claims } where actorId is either the verified preferred_username, email, or oid claim (in that order), ready to pass as actorHumanId.

The two-function shape matches the verifyActor seam defined by ADR-0020: the adapter authenticates (credential → identity) via verifyToken, and authorizes (identity → allowed?) via verifyActor. See @hlao-adapter/google-sso-oidc for the parallel Google implementation.

Configuration

| Field | What it is | | ----------------- | --------------------------------------------------------------------- | | tenantId | Entra tenant id GUID or contoso.onmicrosoft.com suffix. Required. | | clientId | Registered app's Application (client) ID. Required. | | allowedActorIds | Optional allowlist of principals; verifyToken and verifyActor enforce.| | jwksUri | Advanced override; defaults to the tenant's public discovery keys. |

Usage

import { createEntraOidcVerifier } from "@hlao-adapter/microsoft-entra-id";

const entra = createEntraOidcVerifier({
  tenantId: process.env.ENTRA_TENANT_ID!,
  clientId: process.env.ENTRA_CLIENT_ID!,
  allowedActorIds: (process.env.ENTRA_ALLOWED_ACTOR_IDS ?? "")
    .split(",")
    .map((s) => s.trim())
    .filter(Boolean),
});

// Web handler: authenticate the incoming token.
app.post("/reviews/:id/approve", async (req, res) => {
  const { actorId } = await entra.verifyToken(req.headers["x-entra-id-token"] as string);
  await runner.approveReview({ actorHumanId: actorId, ... });
});

// Runner deps: gate approvals on the same identity.
const runner = createRunner({ verifyActor: entra.verifyActor, ... });

Dependencies

  • jose for JWKS + JWT verification (already used across the adapter fleet).
  • zod for config validation.

Testing

Unit tests use a local RSA keypair via jose.generateKeyPair and inject createLocalJWKSet through the jwksGetKey option; no network calls are made. Run with pnpm --filter @hlao-adapter/microsoft-entra-id test.