$ show tetherto/pearpass-app-desktop
PearPass Desktop is an Electron/React password manager with a local-first architecture: encrypted vaults are stored on-device and synchronized peer-to-peer through Pear Runtime, with no central cloud account. The renderer is a large React application handling vault/record CRUD (logins, credit cards, identities, notes, Wi-Fi, passphrases, custom fields), folders, favorites, TOTP authenticator codes, import/export from other password managers, and extensive settings. The Electron main process spawns a Bare-sidecar vault worklet, exposes a preload bridge, and coordinates secure native messaging with a browser extension. The repo also includes Flatpak/Snap/AppImage/MSIX packaging, an Appling installer, and a Playwright E2E suite. Security is taken seriously: there is an encrypted session handshake (X25519 ECDH, Ed25519 transcript signatures, secretbox, sequence numbers), a method registry separating public vs secure IPC methods, master-password verification, auto-lock, and platform-specific clipboard cleanup. The codebase has extensive Jest unit coverage and Playwright E2E coverage for every record type. However, much of the actual vault crypto and UI kit logic lives in internal @tetherto packages, making this repository primarily application glue around private dependencies. Maintainability is mixed. The README explicitly states development is paused, and there are signs of drift: mixed JS/TS, duplicated attachment/schema logic across many modal forms, a frozen legacy UI component tree, commented-out E2E tests, a likely bug in pairing-token hash construction, and feature stubs marked UNSUPPORTED. It remains a well-organized and functional password manager, but a significant refactor would be needed to fully modernize it.
The LLM identified 3 files worth highlighting for reuse:
Implements a complete encrypted session handshake and request protection for native messaging: X25519 ECDH key agreement, Ed25519 transcript signatures, secretbox payload encryption, and sequence numbers/expiry for replay protection. The logic is self-contained, unit tested, and can be reused in any local IPC or extension bridge that needs an authenticated, encrypted channel.
A tested registry that separates public bootstrap methods from secure authenticated methods and gates invocation based on session state/status. It offers a declarative way to expose IPC commands and is reusable for native-messaging servers, WebSocket RPC, or Electron IPC backends.
Installs and uninstalls browser native-messaging host manifests across Windows, macOS, Linux, Snap, and Flatpak environments, including registry keys and wrapper-script generation. It encapsulates a notoriously fragile cross-platform integration and is reusable by any desktop app that wants to expose a native host to browser extensions.