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

@starci/auth

v0.4.0

Published

The sign-in of a StarCi lite app in one package: a NestJS module (EdDSA access tokens with a multi-key JWKS, bcrypt passwords, Google OAuth with state and PKCE, rotating refresh tokens with a reuse grace window and reuse detection, a failures-only sign-in

Readme

@starci/auth

The sign-in of a lite StarCi app: one package, four entries.

| entry | holds | |---|---| | @starci/auth/server | the NestJS module (AuthModule.register / registerAsync), the token signer and verifier (EdDSA, multi-key JWKS), rotating sessions, the sign-in budget, the refresh cookie, the passport flows and the doors that run them | | @starci/auth/client | createAuthClient: access token in memory, one shared refresh, signed out only on 401 or 403 | | @starci/auth/client/react | AuthProvider, useAuthSession, useAuthClient, useWhenSignedIn, useCooldown (context and hooks over the client; no visual) | | @starci/auth/contracts | door paths, wire codes, claim names and answer shapes both sides read | | @starci/auth/testing | test keys, a fake clock, in-memory stores, testAuthOptions |

An app reaches the package only through integrations/passport (back end) and modules/auth/client.ts (front end); the lint refuses passport*, jose, bcryptjs and @nestjs/jwt in an app.

Back end

AuthModule.registerAsync({
    isGlobal: true,
    authenticator: IDENTITY_AUTHENTICATOR, // the token of the app's AuthAuthenticator, resolved from a global module
    inject: [SESSION_STORE, ACCOUNT_DIRECTORY, RATE_LIMIT_STORE],
    useFactory: (sessions, accounts, rate) => ({ ...parsedOptions, sessions, accounts, rate }),
})

The package reads no environment. The app parses its settings (BE-CONFIG-2) and passes typed options; secrets are passed as { reveal(): string } holders or text. The app implements SessionStore over the tables of migrations/identity-sessions.sql (an app whose baseline holds the 0.2.0 tables adds migrations/identity-refresh-raced-successors.sql), AccountDirectory over its account doors (in a StarCi lite app, the managed persistence/account-doors.port.ts over the SECURITY DEFINER be_auth_* functions of the baseline), RateCounter over its shared counter, and AuthAuthenticator (the password and Google decisions) using AuthPasswords and SignInBudget.counted from the module.

Key rotation: list the new key first with its private key, keep the old key with its public key only, deploy, and drop the old key once its access tokens have expired. Every listed key verifies and is published by AuthSessions.jwks().

Front end

// modules/auth/client.ts: the one instance
export const auth = createAuthClient({ apiOrigin: () => apiOrigin() })

Tests

npm test typechecks, lints and runs the node:test specs under 90% line coverage.