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

@bsv/auth

v0.0.1

Published

Signed, expiry-bound, single-use wallet auth proofs for BSV apps.

Downloads

99

Readme

@bsv/auth

Simple, secure wallet login for BSV apps. A client wallet signs a short-lived proof that it controls an identity key; the server verifies the signature, checks freshness, and consumes the proof once. The single-use store is injected, so the library is framework- and database-agnostic.

  • Signature-based — proves control of the wallet's identity key (asymmetric; the server cannot forge it).
  • Expiry-bound — each proof is valid for a short window (default 2 minutes).
  • Single-use — an injected store rejects replays.

A client signs { action, identityKey, expiresAt, nonce } and sends the proof; the server verifies the signature, that the proof is fresh, and that its nonce has not been seen before.

Install

npm install @bsv/auth

Requires @bsv/sdk (>= 2.0).

Usage

Construct a client (frontend) and server (backend) instance with the same optionsprotocol must match on both sides:

// options: { protocol?, windowMs? = 120000, clockSkewMs? = 30000 }
const OPTIONS = { protocol: [2, 'myapp auth'] }

Client

import { AuthProofClient } from '@bsv/auth'

const authClient = new AuthProofClient(OPTIONS)
const proof = await authClient.createAuthProof(wallet, backendPublicKey, 'login')
// POST { walletPubKey, proof } to your login endpoint

Server

import { AuthProofServer } from '@bsv/auth'

const authServer = new AuthProofServer(OPTIONS)
const result = await authServer.verifyAuthProof(serverWallet, proof, 'login', {
  consumeNonce // your single-use store
})
if (!result.valid || result.identityKey !== walletPubKey) {
  // 401
}

The classes are thin wrappers; the same operations are also exported as standalone functions (createAuthProof, verifyAuthProof, checkAuthSigData, createAuthSigData, serializeAuthSigData), each taking a trailing options argument, if you prefer not to instantiate.

consumeNonce records a proof's nonce and returns false if it has already been used (a replay):

// Mongo (TTL collection: unique `nonce`, TTL index on `expiresAt` expireAfterSeconds:0)
const consumeNonce = async (nonce: string, expiresAt: Date) => {
  try { await col.insertOne({ nonce, expiresAt }); return true }
  catch (e: any) { if (e?.code === 11000) return false; throw e }
}

// In-memory (single-instance servers): a Map<nonce, expiresAtMs> with a periodic sweep.

See docs/usage.md for fuller examples.

Notes

  • protocol must match on client and server (it drives key derivation). Names may only contain letters, numbers, and spaces.
  • Replay is bounded to the validity window by the expiry, and fully closed by consumeNonce — keep records only until expiresAt.