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

@columenlabs/lumen-auth

v0.1.165

Published

Lumen's sign-in checks: Cloudflare Access tokens and service tokens, verified in the Worker.

Downloads

27,162

Readme

@columenlabs/lumen-auth

Lumen's sign-in checks for Workers behind Cloudflare Access: verify the token Access signs on every request, in the Worker, so a route stays closed even when the Access application is misconfigured or a request reached the Worker another way. No dependencies: Web Crypto and fetch, so it runs in a Worker, Bun or Node.

  • Docs: https://lumen.columenlabs.com/docs/
  • For agents: https://lumen.columenlabs.com/llms.txt
  • Source: https://github.com/columenlabs/lumen (packages/auth). MIT.

Install

bun add @columenlabs/lumen-auth

Pin it to the same exact version as the other Lumen packages.

Verify an Access token

import { AccessVerifier, accessToken } from '@columenlabs/lumen-auth';

// One per isolate: the team's signing keys are fetched once and kept an hour.
const access = new AccessVerifier({
  teamDomain: 'myteam.cloudflareaccess.com',
  aud: [env.ACCESS_AUD],            // one application's AUD tag, or several (one Worker, several hosts)
});

const who = await access.verify(accessToken(request));
if (!who) return new Response('Not found', { status: 404 });
who.email;         // the person, when a person signed in
who.serviceToken;  // the service token's client ID, when a service token signed in
who.sub;           // Access's subject id

verify returns null for a missing, malformed, expired or wrongly signed token, a token for another application (aud) or another team (iss). Only RS256 is accepted. A key id it has not seen fetches the keys again.

| Export | | |---|---| | AccessVerifier(config, fetch?, now?) | verify(token) → AccessIdentity or null. fetch and now are for tests | | AccessConfig | { teamDomain, aud } | | AccessIdentity | { sub, email?, serviceToken? } | | accessToken(request) | The request's Cf-Access-Jwt-Assertion, if any | | ACCESS_HEADER | 'cf-access-jwt-assertion' |

Who Access lets in stays Access's policy; what each person may do stays the app's own. This package only proves the request came through Access.

Versions

0.x: any minor may break things until 1.0. Every merge to Lumen's main publishes the next patch of every Lumen package; see the releases.