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

@xemahq/oidc-guard

v0.3.0

Published

Framework-agnostic OIDC / JWT verification for Xema — JWKS fetching, issuer-metadata resolution, and signature validation.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

edupedupxema-devxema-dev

Keywords

Readme

@xemahq/oidc-guard

Layer 0 — pure, framework-agnostic OpenID-Connect JWT verification. Zero runtime dependencies (Node crypto + fetch only); zero Xema-domain concepts.

The single, shared implementation of the error-prone bits every Xema service (and every generic submodule) previously copied by hand:

  • JwksVerifier — per-(cacheKey, kid) signing-key cache, exp/nbf checks, optional issuer pinning, RS256/384/512 signature verification. Fail-closed.
  • IssuerMetadataResolver — resolves a provider's jwks_uri from its OIDC discovery document (<base>/.well-known/openid-configuration), so no caller hard-codes a provider-specific keys path. Cached, fail-closed.
  • OidcTokenVerifier — the high-level primitive: discover the JWKS endpoint for a token's realm/issuer and verify the signature + temporal + issuer claims, returning the decoded payload. Callers layer their own realm/role/context handling on top.

Both the in-monorepo JwtVerificationGuard (@xemahq/platform-common) and the independent submodule guards consume this package rather than re-implementing the crypto. Wrapping it in a NestJS guard, an attestation check, or any other transport is the caller's job — this package holds no framework dependency.