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

lucos_aithne_jsclient

v1.1.3

Published

Javascript library for clients of lucos_aithne

Downloads

938

Readme

lucos_aithne_jsclient

Javascript library for clients of lucos_aithne

Shared JS verify-and-classify library for aithne session tokens. See docs/adr/0001-foundational-design.md for the full design and rationale — this README covers usage only.

The library verifies and classifies; the consumer presents. It has a single runtime dependency (jose), reads no process.env itself, and does not depend on any web framework.

Install

npm install lucos_aithne_jsclient

Usage

import { createAithneClient } from 'lucos_aithne_jsclient';

const aithne = createAithneClient({
  origin:      process.env.AITHNE_ORIGIN,   // default 'https://aithne.l42.eu'
  jwksUrl:     process.env.AITHNE_JWKS_URL, // optional dev override (JWKS fetch address only)
  appOrigin:   process.env.APP_ORIGIN,      // this consumer's own origin — trusted as a loginUrl() return target
  environment: process.env.ENVIRONMENT,     // gates the dev-only render-ui bypass
});

// In Express middleware:
app.use(async (req, res, next) => {
  const { outcome, payload, error } = await aithne.verifySession(req.headers.cookie, {
    requiredScope: 'notes:use',
  });

  switch (outcome) {
    case 'authorized':
      res.auth_agent = payload;
      return next();
    case 'forbidden':
      // Valid session, missing scope — render your own styled 403. Do not
      // redirect: re-login yields the same scopeless token.
      return res.status(403).render('forbidden', { requiredScope: 'notes:use' });
    case 'unauthenticated':
      // No token, or a genuine validation failure — redirect to login.
      return res.redirect(302, aithne.loginUrl(`${process.env.APP_ORIGIN}${req.originalUrl}`));
    case 'unavailable':
      // aithne itself is unreachable — do NOT redirect into a dead aithne.
      // Render your own local "sign-in unavailable" page instead.
      console.warn('aithne unavailable:', error.message);
      return res.status(503).render('unavailable');
  }
});

verifyToken(rawToken, gate) is the same primitive without cookie extraction, for callers that already hold a token (e.g. a WebSocket handshake) — it takes identical gate options, so outcome: 'authorized' means the same thing regardless of which function produced it.

See ADR-0001 §2–§5 for the full API surface (hasScope, parseCookies, the outcome enum, and the resilience/logging obligations), and §6 for what is deliberately out of scope for v1 (CSRF middleware, the Bearer/ machine-principal path, WebSocket wiring, non-JS consumers).

Development

npm install
npm test

Tests run on Node's built-in test runner (node --test) — no test framework dependency.