PearPass

PearPass keeps a password and identity vault on your own devices, encrypting passwords, credit cards, secure notes and custom fields before they are written to disk. No provider holds the copy that matters. The README states that active development is currently paused, so anyone adopting it should weigh that.

Sync is where it departs from the usual design. Instead of a central service, the desktop app is built on Pear Runtime and moves credentials directly between your devices over peer-to-peer connections. The interface is React with styled-components, Redux for state and Lingui for translations, while the vault itself lives in separate worker libraries shared with the mobile app and the browser extension.

What the desktop app covers day to day is small and specific.

• Encrypted storage: every entry type is encrypted at rest before it touches the disk.
• Offline access: the vault opens with no network connection at all.
• Password health: strength analysis flags weak entries in the vault.
• Generator: strong, unique passwords created on demand.
• Multi-platform: macOS, Linux and Windows builds, with a mobile app and browser extension alongside.
• Diagnostics: logging is off by default, and the vault worker redacts known sensitive fields before writing.

Building it needs Node at the version pinned in the repository plus the Pear Runtime, after which the app is staged and run through the pear command. Intel Mac builds are deprecated and shipped without official support or testing. The code is Apache 2.0 licensed, and guides for setup, vault management and syncing live in the project documentation.