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

@superfunctions/oauth-storage

v0.0.1

Published

OAuth state and token storage contracts for Superfunctions

Downloads

301

Readme

@superfunctions/oauth-storage

Shared OAuth state and token persistence contracts, adapters, and encryption helpers.

Install

npm install @superfunctions/oauth-storage @superfunctions/db

Quick Start

Production code should persist tokens through EncryptedTokenVault.

import {
  AesGcmTokenCipher,
  EncryptedTokenVault,
  MemoryOAuthStateStore,
  MemoryTokenVault,
} from "@superfunctions/oauth-storage";

const stateStore = new MemoryOAuthStateStore();
const cipher = new AesGcmTokenCipher((keyRef) => {
  if (keyRef !== "oauth-default") {
    throw new Error("unknown keyRef");
  }

  return Buffer.alloc(32, 7);
});

const tokenVault = new EncryptedTokenVault(new MemoryTokenVault(), cipher);

If you want the shared DB abstraction, createOAuthDbStorage(...) builds the stores with the correct default model names:

import { createOAuthDbStorage } from "@superfunctions/oauth-storage";

const { stateStore, tokenVault, models } = createOAuthDbStorage({
  adapter,
});

console.log(models.oauthStates); // oauth_states
console.log(models.oauthTokenVault); // oauth_tokens

Package Boundary

@superfunctions/oauth-storage owns:

  • OAuthStateStore for short-lived redirect state
  • TokenVault for connection-bound token records
  • consent and revocation-failure stores
  • in-memory, SQL, and @superfunctions/db adapters
  • EncryptedTokenVault, TokenCipher, and AesGcmTokenCipher

It does not decide when to start OAuth, exchange tokens, or expose HTTP endpoints.

Production Notes

  • The default SQL/DB token model name is oauth_tokens.
  • MemoryOAuthStateStore and MemoryTokenVault are fine for tests and small prototypes, but not for multi-instance production deployments.
  • Prefer EncryptedTokenVault for durable token storage so plaintext token JSON never becomes the long-lived record format.
  • If you already use a custom token table/model name, keep passing models.oauthTokenVault until your schema migration is complete.

Related Packages