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

@mayurajs/auth-clerk

v1.2.0

Published

Clerk session tokens as Mayura server identities, verified with Clerk's published keys or its PEM key.

Readme

@mayurajs/auth-clerk

Clerk session tokens as Mayura server identities: verified with your instance's published keys (or its PEM key, with no network), on any runtime, with no dependency.

npm install mayura @mayurajs/auth-clerk
import { mapCapabilities, principalId } from 'mayura/auth';
import { clerkAuthenticator } from '@mayurajs/auth-clerk';

const authenticate = clerkAuthenticator({
  publishableKey: 'pk_live_...',                    // or frontendApi: 'https://clerk.example.com'
  authorizedParties: ['https://app.example.com'],   // the origins your users sign in from
  identity: session => session.orgId ? {
    principalId: principalId('clerk', session.userId),
    projectId: session.orgId,
    agentIds: ['support'],
    capabilities: mapCapabilities(session.orgPermissions, {
      'org:agents:use': ['runs:submit', 'runs:read'],
      'org:agents:operate': ['workflows:read', 'workflows:control'],
    }),
  } : null,
});
// createAgentServer({ ..., authenticate })
  • What is checked. RS256 tokens issued by your Frontend API (read from the publishable key), signed with its keys from /.well-known/jwks.json (or jwtKey, your PEM public key, with no network), within their 60-second lifetime (5 s of clock skew, as Clerk's SDK). Their azp must be one of authorizedParties (Clerk tokens carry no audience; this is what stands for it, against CSRF); false turns that off only where no browser is involved. Sessions Clerk marks pending are refused unless allowPending.
  • What you get. identity receives the session: userId, sessionId, status, the active organization (orgId, orgSlug, orgRole as org:admin) and the user's orgPermissions there (org:<feature>:<permission>), decoded from version 2 tokens' feature bitmasks exactly as Clerk's SDK decodes them, or read from version 1 tokens; actor when someone is impersonating the user; and the raw claims. Nothing is granted unless identity grants it.
  • clerkFrontendApi(publishableKey), clerkSession(claims) and clerkPermissions(claims) are exported for your own checks.
  • Options: publishableKey or frontendApi, jwtKey, authorizedParties, identity, allowPending, clockSkewMs, maxIdentityMs (60 s), fetch.

See Authentication and API keys. Apache-2.0.