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

@tokendance-os/auth-bridge

v0.0.1

Published

High-level Tutti auth helpers for browser apps and Node/Electron clients.

Readme

@tokendance-os/auth-bridge

High-level Tutti auth helpers for browser apps and Node/Electron clients.

Shared contract

Clients that implement their own platform-specific account UI can reuse the canonical account defaults without importing Browser or Node runtime behavior:

import {
  DEFAULT_ACCOUNT_BASE_URL,
  DEFAULT_APP_ID
} from "@tokendance-os/auth-bridge/shared";

Keep compatibility identifiers in this shared contract rather than copying their literal values into product clients.

Browser

import { createTuttiBrowserAuthClient } from "@tokendance-os/auth-bridge/browser";

const auth = createTuttiBrowserAuthClient();

auth.login();
const user = await auth.getUserInfo();
await auth.logout();

Node

import { createTuttiNodeAuthClient } from "@tokendance-os/auth-bridge/node";

const auth = createTuttiNodeAuthClient({
  authJsonPath,
  appCallbackUrl,
  accountHeaders: { "x-environment-lane": "example" }
});

const { session, user } = await auth.login();

accountHeaders adds host-owned headers to Account API requests. The bridge always owns and overwrites its JSON content negotiation and Desktop session cookie headers.

Local Desktop Callback

The Node bridge starts a loopback HTTP server for desktop sign-in. New desktop OAuth completions use:

  • GET /oauth/callback?state=<base64url>&transfer_code=<code>
  • GET /oauth/callback?state=<base64url>&error=<providerError>
  • GET /oauth/callback?state=<base64url>&error=user_cancelled

The callback validates the signed login state, redeems the desktop transfer code through the account service, writes auth.json, fetches user info, and redirects the browser back to the web result page:

/auth/login/callback?desktopBridgeStatus=success&openAppUrl=<safe-deeplink>
/auth/login/callback?desktopBridgeStatus=error&desktopBridgeError=<safeCode>&openAppUrl=<safe-deeplink>

openAppUrl is only used to focus or reopen Tutti. It is sanitized to the allowed app schemes and must not carry transfer_code, sessions, or tokens.

An explicit user_cancelled callback is preserved as a typed cancellation for Node/Go consumers and returns the safe Web result code userCancelled. Cancellation results intentionally omit openAppUrl, so the Web result page can keep the user in the browser. Other callback errors continue to use the safe providerError result code.

/oauth/health and POST /oauth/complete remain available for compatibility with older web clients, but the current web flow redirects the browser to /oauth/callback instead of fetching the local bridge.