@columenlabs/lumen-auth

中文文档
0.1.219发布于 2026/11/09MITTypeScriptES Module零依赖近 30 天下载 4万

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

原始使用文档
文档目录3 节
  1. Install
  2. Verify an Access token
  3. Versions

@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.

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.

版本与发布记录

@columenlabs/lumen-auth 共发布 190 个版本,首次发布于 2026/10/25;过去 12 个月发布了 190 个版本。

版本发布日期距今
0.1.219latest2026/11/091 天前
0.1.2182026/11/091 天前
0.1.2172026/11/091 天前
0.1.2162026/11/091 天前
0.1.2152026/11/091 天前
0.1.2142026/11/091 天前

关于 @columenlabs/lumen-auth 的常见问题

@columenlabs/lumen-auth 是什么?

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

如何安装 @columenlabs/lumen-auth?

在项目目录运行 npm install @columenlabs/lumen-auth,或使用 pnpm add / yarn add / bun add。

@columenlabs/lumen-auth 支持 TypeScript 吗?

支持。包内自带 TypeScript 类型声明(package.json 声明了 types 入口),安装后即可获得类型提示,无需再安装 @types 包。

@columenlabs/lumen-auth 支持 ESM 还是 CommonJS?

以 ES Module 形式发布,推荐使用 import 引入。在 CommonJS 项目中,Node.js 20.19+ / 22.12+ 可以直接 require() 不含顶层 await 的 ES Module,更早的版本需要改用动态 import()。

@columenlabs/lumen-auth 可以商用吗?

@columenlabs/lumen-auth 使用 MIT 许可。宽松许可:允许商业使用、修改和再分发,通常只需在分发时保留原版权与许可声明。以上为概括,不构成法律意见,请以许可原文为准。

@columenlabs/lumen-auth 的下载量有多少?

根据 npm 官方下载统计,@columenlabs/lumen-auth 在 2026/10/11 – 2026/11/09 这 30 天内被下载 40,080 次,日均约 1,336 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@columenlabs/lumen-auth 还在维护吗?

最新版本 0.1.219 发布于 2026/11/09(1 天前);至今共发布 190 个版本,其中过去 12 个月发布了 190 个;首次发布于 2026/10/25。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。