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

@serafort/react-elements

v0.1.0

Published

Clerk-style drop-in styled React components (<SignIn/>, <LoginBox/>, <UserProfile/>) for Serafort authentication, built on @serafort/react-sdk + MUI v7.

Readme

@serafort/react-elements

Clerk-style drop-in styled components for Serafort authentication: <SignIn/> / <LoginBox/>, <MfaChallenge/>, and <UserProfile/>. Built on @serafort/react-sdk's headless hooks + MUI v7. Uses theme tokens throughout — no hardcoded colors.

Quickstart

import { SerafortProvider } from '@serafort/react-sdk'
import { LoginBox } from '@serafort/react-elements'

function App() {
  return (
    <SerafortProvider domain="auth.acme.com" publishableKey="pk_live_...">
      <LoginBox />
    </SerafortProvider>
  )
}
import { useUser, useSession } from '@serafort/react-sdk'

function AccountMenu() {
  const { user, isLoaded } = useUser()
  const { signOut } = useSession()

  if (!isLoaded) return null
  if (!user) return <a href="/sign-in">Sign in</a>

  return (
    <div>
      {user.email}
      <button onClick={() => signOut()}>Sign out</button>
    </div>
  )
}

(useUser/useSession are re-exported here from @serafort/react-sdk for convenience — install @serafort/react-sdk directly if you only need the headless hooks without any styled UI.)

Components

  • <SignIn/> — email → SSO-domain auto-routing → password or passkey → MFA challenge. Unstyled container, styled controls.
  • <LoginBox/> — <SignIn/> inside a themed card. The <LoginBox/> from the plan.
  • <MfaChallenge/> — standalone MFA entry screen (TOTP / SMS / recovery code); also rendered automatically inside <SignIn/> when a challenge is pending.
  • <UserProfile/> — self-serve password change, active-session review and revocation, TOTP enrollment/disable, and passkey management.
  • <SerafortThemeProvider/> — optional MUI theme fallback for host apps with no MUI setup of their own.

Theming

Components read colors from the ambient MUI theme (useTheme()) and use CSS custom properties with fallbacks for non-palette values (e.g. var(--sf-radius-lg, 12px)) — the same convention the internal auth module's AuthSocialButton uses. They do not depend on @cap/theme: that package pulls in @cap/platform-core/@cap/platform-store (the internal app's Zustand store, tenant theme resolution, IndexedDB persistence), which a third-party host app installing this package from npm has no use for. See the comment header in src/theme/tokens.ts for the full rationale.