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

@nostr-wot/identity

v1.2.0

Published

Accounts, encrypted vaults, passkeys, signing policies and remote signer hosting for Nostr.

Readme

@nostr-wot/identity

Build the account and approval boundary of a Nostr signer. This package owns seed derivation, portable encrypted vaults, permission records, the signing pipeline and the NIP-46 responder. Use it in an extension, mobile signer or server that controls accounts. Applications that only request signatures should use nostr-wot-sdk/signers.

Identity package: these entry points replace accounts, vault, permissions, signer-core and bunker packages in the consolidation release. Publish this replacement before deprecating the old npm names. See the migration guide.

Install

npm install @nostr-wot/identity nostr-wot-sdk nostr-tools

Use ESM imports. Import explicit subpaths to identify the boundary you are using; @nostr-wot/identity/vault is an import path, not a separate package to install.

Entry points

| Import | Use case and detailed guide | | --- | --- | | @nostr-wot/identity/accounts | Generate/import accounts, derive NIP-06 keys, classify imported material, and encrypt/decrypt NIP-49 keys. | | @nostr-wot/identity/vault | Password vault lifecycle, scoped secret access, passkey records and recovery. | | @nostr-wot/identity/permissions | Caller and method rules, site scopes and destination-specific authentication grants. | | @nostr-wot/identity/signing | Authorize requests, request approval/unlock, sign locally or delegate to a remote signer, and report typed errors. | | @nostr-wot/identity/bunker | Serve NIP-46 clients over NIP-44 encrypted relay transport. |

Recognize imported account material

import { detectImportKind, generateMnemonic, validateMnemonic } from '@nostr-wot/identity/accounts';

const mnemonic = generateMnemonic();
if (!validateMnemonic(mnemonic)) throw new Error('Invalid mnemonic');
const kind = detectImportKind(mnemonic);

Generating or parsing an account does not persist it, authorize requests or display a backup flow. The host supplies those decisions. Never log a mnemonic or private key. The account guide documents accepted input, derivation paths and import errors.

Compose a signer host

Use a persistent KeyValueStore from your host with the vault and permission store; nostr-wot-sdk/storage supplies the interface, a namespacing wrapper and an in-memory implementation for tests. Give SignerCore the vault, permissions, approval UI and any remote-signing or unlock ports your host supports. Route verified transport requests to it. A NIP-46 BunkerServer receives and decrypts requests, but its injected handler remains responsible for authorization.

A deny rule ends a signing request before approval. The core pins the account and rechecks authorization around asynchronous boundaries. Batch results report each item's success or failure; do not treat a partially successful batch as if nothing was signed. When composing with the bunker, use handlerTimeoutMs: 0 so the signing pipeline owns request timeouts.

Vault and passkey responsibilities

The password vault uses PBKDF2-HMAC-SHA-256 and AES-256-GCM with an existing versioned record format. An empty password provides no secrecy against someone holding the stored record. Secret accessors give callbacks temporary byte copies and invalidate results after revocation; callbacks must not publish or otherwise externalize secrets or results before authorization completes. The host owns storage durability, unlock UI and lock/session lifetime.

Passkey version 2 records use separate helpers; do not pass them to the password-only Vault.unlock(). The host performs WebAuthn registration/assertions, obtains PRF output, verifies the user and coordinates mutations. Recovery is not automatically a relay upload: provider-confirmed storage and explicit fallback behavior are described in the passkey recovery guide. resolvePasskeyIdentity logs in with a discoverable passkey in either derived or stored mode, classifying its user handle first so a stored passkey never yields a derived key; an untagged passkey with no evidence either way comes back ambiguous for the user to confirm. saveStoredRecord writes key or vault records for tagged stored passkeys using provisional event kind 31778; seed inputs are normalized to a vault and legacy records remain readable. The same guide covers both.

Authentication is destination-specific

NIP-42 and NIP-98 signing is credential issuance. A broad event-kind allow is insufficient. Supply transport-attested requester identity and display the parsed destination and method in approval UI. Web requesters require one-time consent by default; remembered grants are explicit policy. Malformed destinations, revoked permissions, changed accounts and stale requests fail rather than bypass approval. See the signing guide for AuthenticationPolicy, remembered grants and the host-only relay login path.

Runtime requirements

Portable account, vault, permission and signing code does not depend on the DOM or WebExtension APIs. Hosts supply storage, clocks where configurable, approval and transport adapters. Required globals include TextEncoder, TextDecoder, secure crypto.getRandomValues, timers and AbortController. Post-quantum paths also need base64 support (atob/btoa, or the supported Buffer fallback). React Native/Hermes hosts must install the appropriate polyfills before loading the modules, including secure randomness; do not substitute a non-cryptographic random source.

The portable vault's cryptography does not require crypto.subtle. Browser WebAuthn and provider adapters still require their documented platform capabilities. A relay responder also needs a compatible WebSocket transport. Import only the entry point appropriate to your runtime.

License

GNU General Public License version 3 only (GPL-3.0-only). See LICENSE and NOTICE.