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

@softwareshaker/auth-client

v0.1.3

Published

Shared authentication client for SoftwareShaker applications.

Readme

@softwareshaker/auth-client

Shared authentication client for SoftwareShaker applications.

Installation

npm install @softwareshaker/auth-client

Entry points

  • @softwareshaker/auth-client provides application-access token helpers and shared types.
  • @softwareshaker/auth-client/react provides the Better Auth React client and impersonation banner.
  • @softwareshaker/auth-client/server provides the server-side OAuth and application-access flow.

The clientSecret and jwtSecret options belong exclusively in server-side code. Never expose them through browser environment variables or client bundles.

Server-side renewal

The server flow requests offline_access and keeps OAuth credentials in secure, HTTP-only cookies. The auth server and registered OAuth client must allow the refresh_token grant. Existing sessions receive these cookies after their next sign-in.

requireFirstPartyAppAccess renews expired application tokens before returning an authorized result, so the original request body remains available to the application's action. The auth server still checks the underlying session and current application assignment when issuing a replacement token.

Forward every Set-Cookie header from authorized results, as well as redirect and forbidden results, to the browser. Use request-scoped server state or middleware to share the result across loaders and actions. Never serialize these headers into page data. Preserve cookie deletions made by logout or organization switching over earlier renewal cookies.

If issuing an application token fails after OAuth credentials have rotated, AppAccessRequestError.headers carries the replacement cookies. Forward those headers on the error response so the next request can retry with the current credentials.

Concurrent OAuth refreshes are deduplicated within one server process, with successful results retained for 30 seconds to cover overlapping requests. Deployments with multiple processes must serialize refreshes for each session across those processes or use a provider with refresh-token reuse handling before enabling renewal across replicas.