peach-browser
A free, open source, local-first password manager for Chrome, Firefox, and Android.
TypeScript
timeline
atlas420 files
crypto-core/
fixtures/
public/
codex/
scripts/
build-noise-core.mjsbuild-peachscript.pyBuild PeachScript-Regular.otf — 256 historical-runic glyphs.bun-ambient.d.tsAmbient declarations for the Bun APIs the release scripts use.check-cross-client-adoption.test.tscheck-cross-client-sync.mjscheck-extension-surface.mjscheck-noise-core.mjsPB-26-003: verify the committed Noise WASM still matches crypto-core source.check-sw-static-imports.mjsFails the build if any chunk reachable from the MV3 service worker still contains a runtime
import().ci.tsclean-chrome-dist.mjsclean-firefox-artifacts.mjscross-client-gradle.init.gradlegenerate-kat.mjsgenerate-kat.mjs — recompute the pinned ciphertext for self-test.ts (PCH-01-020).manifest-parity.test.tsPB-26-610 — the source manifests are security-reviewed; the built manifests are what ships.package-source.test.tspackage-source.tsprocess-readiness.d.mtsTypes for the plain-JavaScript readiness helper (PB-26-904).process-readiness.mjsprocess-readiness.test.tsrelease-firefox.tsrelease-gate.test.tsrelease-gate.tsPB-26-210: Release browser-gate validation.release-lib.test.tsscripts/release-lib.test.ts PB-26-211: release tool hardening — security tests for the argv-based runner.release-lib.tsscripts/release-lib.ts Shared argv-based runner for release tooling (PB-26-211).release.test.tsrelease.tsroot-derivation-gate.test.tsCampaign task 2.4 — no shipping source may derive device key material from the vault root.run-release-browser-gate.tstest-firefox-passkeys.mjstest-firefox-sender-context.mjsweb-accessible-resources.test.tssrc/
background/
aes.test.tsaes.tsaes.ts — AES-256-GCM encrypt/decrypt primitives for vault storage.alarms.test.tsalarms.tsclipboard.double-failure.test.tsT-037: clipboard double-failure / alreadyWritten pathclipboard.test.tsclipboard.tsClipboard write + reliable auto-clear — audit fix HV-2.codex-handlers.test.tsTests for src/background/codex-handlers.ts.codex-handlers.tscodex-handlers.ts — message handlers that back the Peach Codex flow.commands.test.tscommands.tsKeyboard command handler — routing for summon-inline: 1.device-identity.test.tsdevice-identity.tsLocal-device identity helpers.entry.lock-port.test.tsThe lock-on-close onConnect listener accepts only our nonce'd "popup-<uuid>" port from the extension page and ignores anything else.entry.tshealth.test.tshealth.tshealth.ts — Pro advanced vault health analysis.license.tslicense.verification.test.tsT-009: License Ed25519 signature verificationlocked-sync-spool.test.tslocked-sync-spool.tsmesh-relay-listener.test.tsmesh-relay-listener.tsmessage-policy.test.tsmessage-policy.tsmessages.adversarial.test.tsmessages.adversarial.test.ts — Layer 3 §3.3 adversarial message handler tests.messages.autolock-refresh.test.tsPB-26-107: passive page traffic must not refresh the auto-lock timer.messages.batch-sanitize.test.tsT-008: PCH-01-016 batch-add canary/tag sanitizationmessages.create-vault-from-root-key.test.tsmessages.edit-origin.test.tsT-022: GET_ENTRY_FOR_EDIT via sender.url + locked-vault AUTOFILL_QUERYmessages.entry-write-origin.test.tsPB-26-106: content-script entry mutations must be bound to the entry's own domain set.messages.passkey-offer-decline.test.tsPB-26-109: the passkey offer-decline handler is page-relay, so any page's content script may send it.messages.test.tsmessages.tsmessages.ts — the only background message handler.ml.predictbatch.test.tsT-030: ml.ts predictBatch — batch sizes, softmax stability with extreme weightsml.tsnotes.test.tsoffscreen.htmloffscreen.tsOffscreen document script — audit fix HV-2c.pair-secrets.test.tspair-secrets.tspair-secrets.ts — PB-26-213: the reusable rendezvous secret must never sit in plaintext in chrome.storage.local.paired-devices.test.tspaired-devices.tsPaired-device registry — v3 sync.passkey-chrome-ceremony.test.tspasskey-chrome-ceremony.test.ts — covers the Chrome chrome.webAuthenticationProxy ceremony path that the Firefox-proxy test file does NOT exercise.passkey-crypto.test.tspasskey-crypto.tspasskey-deny-on-close.test.tspasskey-deny-on-close.test.ts — M8/COR-009passkey-firefox-proxy.test.tspasskey-firefox-proxy.test.ts — covers the v2.12.0 Firefox content-script proxy path.passkey.ed25519.test.tsT-015: Ed25519 passkey round-trippasskey.tspending-adoption-holder.test.tspending-adoption-holder.tspending-vouched-devices.test.tspending-vouched-devices.tsPending vouched devices — audit fix MV-7.recovery-pending.test.tsrecovery-pending.tsBackground-owned state set while the user has just created or rotated a vault identity and is confirming their recovery words.recovery-words.test.tsrecovery.adversarial.test.tsrecovery.adversarial.test.ts — Layer 3 §3.2 adversarial recovery words tests.relay-adoption-bg.test.tsrelay-adoption-bg.tsself-test.test.tsself-test.tsself-test.ts — Known-Answer Test (KAT) for the Peach crypto stack.storage-access.test.tsstorage-access.tsPB-26-203: the session-key escrow is only as trustworthy as the boundary around chrome.storage.session.sync-alarm.test.tssync-alarm.tssync-alarm.ts — the 10-minute background sync tick.sync-alerts.test.tssync-alerts.tsPending sync security alerts.sync-coordinator.test.tssync-coordinator.tsVault sync — Phase 2 manifest-diff coordinator.sync-generation.test.tsThe §11 secure-reset contract: the durable generation record, the six states, create-on-miss refusal, archival by generation, crash recovery at every step, and the sync gate.sync-generation.tsThe durable Sync-generation record and its state machine (protocol §11).sync-runner.test.tssync-runner.tsProduction sync runner — composes the live vault adapter, WebSocket transport, and coordinator into the function the dispatcher injects via
setSyncRunner.sync-settings.test.tssync-settings.tssync-static.test.tsIV.7 — Static safety assertions for vault sync.sync-trigger.test.tssync-trigger.tssync-trigger.ts — central sync dispatcher.sync-vault-adapter.test.tssync-vault-adapter.tsProduction adapter that backs runSyncInitiator with the live vault.vault-createVaultFromRootKey.test.tsvault-history.test.tsVault history tests.vault.adversarial.test.tsvault.adversarial.test.ts — Layer 3 §3.1 adversarial vault tests.vault.card-decline.test.tsPB-26-108: declined-card metadata must not be offline-enumerable.vault.consolidate-passkeys.test.tsT-023: vault.consolidatePasskeyEntries — passkey merge with lastUsed rankingvault.corruption.test.tsT-018: Vault corruption vs wrong-password discrimination (M7/COR-007)vault.duress-adoption.test.tsvault.entry-id-namespace.test.tsvault.hibp-padding.test.tsPCH-02-007 regression tests — the HIBP k-anonymity range request must ask for response padding, and the parser must stay correct on padded responses.vault.purge-trash.test.tsT-024: vault.purgeExpiredTrash — retention cutoff boundaryvault.rotate-sync-identity.test.tsT-016: rotateSyncIdentity — new root key, cleared peers, recovery pendingvault.session-escrow.test.tsvault.sync-clamp.test.tsUnit tests for HV-1 — sync timestamp clamp + remote-mutation alerts.vault.test.tsvault.tombstone-ledger.test.tsvault.tsvault.ts — sole owner of vault state and chrome.storage vault keys.vault.update-entry-sanitize.test.tsPCH-02-001 regression tests — UPDATE_ENTRY patch path must route canary/tags/passkey through the same sanitizers the add/restore/sync funnels use (sanitizeCanary / sanitizePasskey / sanitizeTags).content/
passkey-toast/
crypto/
argon2.test.tsargon2.tsargon2id.kat.test.tsT-019: Argon2id known-answer test (KAT) + parameter assertioncrypto.test.tsdecompression-bomb.test.tsMV-4: decompression-bomb output bounds on the zstd and pako legs.official-vectors.test.tspeachPayload.binaryreader-bounds.test.tsPCH-02-008 regression tests — BinaryReader must bound every read and fail with the decoder's existing PAYLOAD_TOO_SHORT code on truncated input.peachPayload.bomb.test.tsT-005: peachPayload declared-length decompression bomb (MV-4)peachPayload.test.tspeachPayload.tspeachPayload.ts — binary payload format shared by PeachScript and the Peach QR matrix code (spec §2).peachScript.bounds.test.tsPB-26-208: PeachScript normalization before limits.peachScript.test.tspeachScript.tspeachScript.ts — PeachScript encoding/decoding.totp.rfc6238.test.tsT-004: TOTP RFC 6238 known-answer vectorstotp.test.tstotp.tszstd.tsThin wrapper around @bokuweb/zstd-wasm that defers WASM load until the first compress/decompress call and memoises the init promise.
popup/
codex/
aztec.tsaztec.ts — Aztec 2D barcode generation with round-trip verification.browser-bundle.test.tscodex.adversarial.test.tscodex.adversarial.test.ts — Layer 3 §3.4 adversarial Codex tests.codex.multistripe.test.tsT-017: Codex multi-stripe round-tripcodex.suite.test.tscodex.suite.test.ts — cross-cutting regression suite for the Codex pipeline.codex.test.tsconfirmation.tsPick 3 distinct positions in [1, 12] for the recovery-words confirmation gate.erasure.tserasure.ts — Reed-Solomon erasure coding around the WASM library.generate.test.tsgenerate.tsgenerate.ts — full Codex generation pipeline.helpers.tshelpers.ts — shared utilities for Codex generation and restoration.node-wasm.tsNode-only WASM byte loader for Vitest.pdf-import.clamp.test.tspdf-import.sandbox.test.tsT-007: MV-9 pdf.js sandbox flags regression testpdf-import.test.tspdf-import.test.ts — coverage for the testable surface of the PDF import path.pdf-import.tspdf-import.ts — restore from a Codex PDF instead of a camera scan.pdf-layout.tspdf-layout.ts — A4 Codex page geometry shared between the generator and the PDF importer.pdf.tspdf.ts — render the printable Codex PDF.reed-solomon.tsBrowser-safe wrapper around the Reed-Solomon WASM exports.restore.test.tsrestore.test.ts — coverage for ChunkBuffer, parseRawScan, reconstructAndVerify.restore.tsrestore.ts — Peach Codex restoration library (popup-side).rs-loader.tsrs-loader.ts — load the Reed-Solomon erasure WASM module.scan-limits.test.tsscan-limits.test.ts — PB-26-207 resource bounds on the Codex scan path.scanner.tsscanner.ts — camera-based Aztec scanning for Codex restoration.
components/
GeneratorDrawer.test.tsGeneratorDrawer.tsxNoteRow.test.tsx@vitest-environment jsdomNoteRow.tsxNoteToolbar.tsxPairingBirds.tsxPairing birds — the two illustrated characters used on the pairing screens.PairingProRequired.tsxPairingQrCode.tsxPeachMark.tsxRecoveryRuneBackground.tsxRuneBackground.tsxRuneCanvas.tsxSyncModeSelector.test.tsx@vitest-environment jsdomSyncModeSelector.tsxSyncModeSelector — the one place the relay choice is made.
views/
Add.tsxAdoptVaultView.test.tsx@vitest-environment jsdomAdoptVaultView.tsxCodexGenerateView.test.tsx@vitest-environment jsdomCodexGenerateView.tsxPeach Codex — generation view.CodexRestoreView.test.tsx@vitest-environment jsdomCodexRestoreView.tsxPeach Codex — restoration view.contracts.test.tsx@vitest-environment jsdomEntry.totp-params.test.tsx@vitest-environment jsdomEntry.tsxExport.csv.test.ts@vitest-environment jsdomExport.tsxSignal-conditioned views in this file must use <Show>, never a signal-conditioned early return (
if (signal()) return <X/>).Health.test.tsx@vitest-environment jsdomHealth.tsxImport.test.tsx@vitest-environment jsdomImport.tsxSignal-conditioned views in this file must use <Show>, never a signal-conditioned early return — see Projects.md §4.1.InitialSyncView.test.tsx@vitest-environment jsdomInitialSyncView.tsxLock.test.tsx@vitest-environment jsdomLock.tsxNoteEditor.toHtml.test.ts@vitest-environment jsdomNoteEditor.tsxNotesEditor.tsxNotesMode.tsxNotesTOC.tsxOnboarding.tsxPairDevice.test.tsx@vitest-environment jsdomPairDevice.tsxPairDevice — the pairing surface, opened from the Settings → Sync card.Panic.tsxPasskeyApproval.tsxProCelebration.tsxProNudge.test.tsx@vitest-environment jsdomProNudge.tsxRecoveryWordDisplay.tsxRecoveryWordEntry.tsxSettings.tsxTrashView.tsxvault-search.test.tsvault-search.tsVault.tsxview-test-utils.tsxWhatsNew.tsxzxcvbn-strength.test.tsLV-8: the @zxcvbn-ts replacement must score the master-password strength meter on the same 0-4 scale as the old zxcvbn, with dictionaries loaded (language-common is what keeps weak passwords from scoring optimistically).shared/
noise-core-wasm/
any is intentional throughout this module (L17/I3/QUA-010): import files are user-supplied external JSON whose schemas vary by source app and version (1Password CPG, Bitwarden, CXF, generic CSV).initial-sync.test.tsinitial-sync.tslegacy-identity-derivation.test-support.tsRoot→device key derivation, retained for tests only — campaign task 2.4.mesh-peer-role.tsml.tsnoise-blake2s-kat.test.tsnoise-core.tsnoise-js.test.tsNoise NK auth proof regression test.noise-js.tsNoise NK initiator for browser-to-browser sync.noise-kk.test.tsnoise-small-order-dh.test.tsPB-26-014 follow-up — the JS-side DH boundaries in noise-js.ts mirror the Rust core's small-order X25519 blocklist (libhydrogen's contributory-behaviour list).noise.reject-zero-dh.test.tsPCH-02-009 regression tests — every Noise NK DH must reject an all-zero shared secret (low-order / identity peer point) instead of feeding it into the key schedule.pairing-dial.test.tspairing-dial.tsThe WebSocket seam every relay-facing Peach flow shares.pairing-handshake.tsShared pairing primitives used by the live relay-adoption path.pairing-invitation.test.tspairing-invitation.tspasskey-flags.tspasskey-flags.ts — single switch for the Firefox passkey content-script proxy.passkey-utils.test.tspasskey-utils.tspasskey-utils.ts — WebAuthn relying-party-id validation.pro-nudge.test.tspro-nudge.tsrecovery-word-list.tsrecovery-word-list.ts — 2048-word recovery word list for Peach vault recovery.recovery-words.checksum.test.tsT-002: BIP39 checksum rejectionrecovery-words.cross-platform.test.tsrecovery-words.integrity.test.tsT-001: BIP39 word-list integrityrecovery-words.kek.test.tsT-003: 128-bit prefix-KEK invariant (PCH-01-005 sibling)recovery-words.tsrecovery-words.ts — BIP39-compatible recovery word encoding for Peach vault recovery.release-notes.test.tsrelease-notes.tsCurated release history and post-update notice selection.rendezvous.test.tsrendezvous.tsshortcuts.test.ts@vitest-environment jsdomshortcuts.tsshortcuts.ts — keybinding schema, defaults, matcher, formatter.storage.tssync-entry-envelope.kat.test.tssync-identity.test.tssync-identity.tsSync identity — vault-scoped primitives.sync-kk-transport.test.tssync-limits.tsSync trust + resource bounds — audit fixes HV-1 (timestamp clamp) and MV-3 (receive-path size bounds).sync-outcome.test.tssync-outcome.tsWhy a sync run ended, in a form both the service worker and the popup can name.sync-padding.test.tssync-padding.tsE7: frame padding at the relay boundary.sync-transport.tsWebSocket reconnect transport — Noise KK with both paired static keys.sync-types.tsVault sync — type definitions.sync.disconnect.test.tsT-020: WebSocket sync-disconnect handling (PCH-01-026 #9)types.tstypes.ts — cross-boundary types and the MessageType union.vault-adopt-snapshot.test.tsvault-adopt.test.tsvault-adopt.tstest/
tests/
fixtures/
history
5e5b58af45b5receiver auto-accepts the SAS in inverse pairing: both sides derive it from the same Noise handshake hash, so the codes match by construction. Receiver returns true from confirmSas immediately, drops the ADOPTION_SOURCE_SAS push, removes the popup's SAS phase and the RECEIVER_SAS_DECISION round-trip. Phone's 'They match' is the single user gate. Deleted waitForSasConfirmation, resolveReceiverSasConfirmation, the pendingSasConfirmation slot, and the receiver timeout. Updated test fixtures to match. (v4.3.15)3 months ago588994063c7freceiver session was swallowing the real error in its catch block. Log the actual exception via console.error and surface the message in the ADOPTION_SOURCE_RESULT push so the popup shows the real failure instead of the generic 'adoption_failed'. Bump to v4.3.15 to actually publish the logging change. (v4.3.15)3 months ago55d8aadfbe09receiver session was swallowing the real error in its catch block. Log the actual exception via console.error and surface the message in the ADOPTION_SOURCE_RESULT push so the popup shows the real failure instead of the generic 'adoption_failed'. (v4.3.16)3 months agoe97b03ea682asource flow SAS gate: START_ADOPTION_SOURCE now actually waits for the popup to confirm the 8-digit code instead of auto-approving. Mirrors the receiver's id-keyed deferred pattern (SOURCE_SAS_DECISION). Both pairing flows now have symmetric, real SAS gates. (v4.3.15)3 months agoecedb447300fPairingBirds were overlapping on the 'Add a new device' screen — 220px stage held two 108px birds at 28px inset (52px overlap). Widened the stage to 300px and moved the birds in to left/right 12px so they sit ~60px apart. (v4.3.14)3 months agoa4750a51db3cbrowser receiver loop: START_ADOPTION_RECEIVER now accepts the phone's Noise dial, receives ADOPT_GRANT, calls CREATE_VAULT_FROM_ROOT_KEY with the popup-supplied password, and pushes ADOPTION_SOURCE_RESULT. SAS confirmation goes through a new RECEIVER_SAS_DECISION message: the popup confirms via the same chrome.runtime.onMessage pipe the existing source flow already uses. AdoptVaultView re-adds the sas/success/error phases it dropped in the earlier simplification. Source-side requestConsent left as-is (TODO in task brief; touching it would change the existing source-flow test expectations). (v4.3.14)3 months ago146d23dcd148invitation carries vaultStatus: 'empty' for the onboarding receiver (no vault) and 'populated' for the Sync settings source (has vault). The phone reads this to decide its role — source or receiver — instead of guessing. Older invitations without the field parse as 'populated' (the historical default) so the existing sync is unaffected. (v4.3.13)3 months agof65d67bbb5baonboarding: reverse the QR flow. The empty extension now shows a QR (the phone scans it) instead of scanning the phone's QR. New START_ADOPTION_RECEIVER message in the background holds the rendezvous without needing a vault, and AdoptVaultView displays the result. UI-only — the phone-side reversal (sending the vault back over the existing channel) is a separate change. (v4.3.12)3 months agoee7c66358190restore the Sync settings birds: the onboarding testicle-look was the only complaint. Restored PairingBirds.tsx, the birdStage function in PairDevice.tsx, the test assertion, and the bird CSS block. (v4.3.11)3 months ago3f5891a8b076onboarding cleanup: drop the bird-pair avatars from AdoptVaultView (pair and success phases) and PairDevice — the two circles on a bar looked like testicles. Trashed PairingBirds.tsx, removed its first CSS block. Drop the 'Already have a backup?' section from Lock.tsx — the welcome screen already asks, and the test for it. (v4.3.10)3 months ago58c7a0bdb8f3notes mode: move new-note affordance from the bottom of the list to the header bar as a + glyph, so a long note list no longer hides the button below the fold (v4.3.9)3 months ago52793d6ded0asettings card scrollbar: pull the body out of the card's right padding so the thumb sits flush with the right edge, and add a matching thin Webkit scrollbar style for Chrome (v4.3.8)3 months ago52ea861750a0Entry view: notes are no longer in its navigation set, counter, or default-selection path; single nonNoteEntries memo and pickNavigable helper make the invariant hold at every fallback (v4.3.7)3 months ago3453e4d02417vault list: long-press now enters multi-select with the held row selected, and the synthesised mobile contextmenu event is suppressed so it doesn't reopen the menu and undo the gesture (v4.3.6)3 months ago88f4c97bcaabtreat a peer-closed WebSocket after entry exchange as a completed sync, not run_failed; classify mid-protocol disconnects as connection_lost (yellow) so the indicator stops turning red on syncs that demonstrably landed (v4.3.5)3 months agoaee880956950fix: Move Sync now to global status (v4.3.4)3 months agoccb6a770acb0fix: Let vault presence direct pairing (v4.3.3)3 months ago3b8b0dd8f317feat: Keep routine sync quiet (v4.3.2)3 months agoc700871e2778feat: Clean up existing-user Sync onboarding (v4.3.1)3 months agodaf6d2a04ad2feat: Simplify Sync Settings with progressive disclosure (v4.3.0)3 months ago399fb468341bfeat: Make pairing single-confirm and atomic (v4.2.18)3 months ago425e41d0ec00docs: Record first live Peach Sync completion3 months agoa7989ee758fefix: Correct large sync frame chunking (v4.2.17)3 months ago5b989b3f66e2fix: Preserve sync timeout stage (v4.2.16)3 months agoc6bed9d2aebedocs: Queue calmer Sync Settings structure3 months ago27e2e647a814fix: Reconcile paired-device revocations on startup (v4.2.15)3 months ago9faf99d62ad3fix: Repair stale paired-device removal (v4.2.14)\n\n- Remove overlapping paired rows even when a terminal revocation already exists\n- Clear old revocations after a fresh SAS-confirmed direct re-pair\n- Add regressions for both live-state shapes3 months agof1785b58565aadd unpair regression: storage revoke + UI refresh — message handler and Settings test3 months agofee1c9e1e62eadd chrome.alarms periodic sync, SW startup hook, and device-list-change trigger; reclassify network-class outcomes from error (red) to warn (yellow); bump to v4.2.133 months ago0f40221cf386fix the v4.2.11 chunking bug: a non-last chunk sliced at MAX then prepended a marker produced 65520-byte plaintexts the crypto core refused, so multi-chunk frames crashed. Now slices at MAX-1 to leave room, and a real-Noise round-trip test pins the invariant (v4.2.12)3 months ago0b24e17342fdfix the broken sync: split a too-large padded frame across Noise messages, mark the first with a continuation byte; padded frame stays 24 MiB, single-chunk path unchanged, and the bucket ladder is now provably under the 65519-byte Noise plaintext limit (v4.2.11)3 months ago4ab2a08223f8search and vault-security match the real UI: escape closes the list rather than clearing it, the filtered-empty list has its own copy, the generator opens from the list, CSP is asserted on the manifest, and four vendor-bundle greps that only ever matched pdf.js and a QR library are gone3 months agof963b19a27a4createEntryViaForm reveals the 2FA and notes fields through their '+ add' links, which is the only way those inputs exist in the new-entry form3 months agocb6120398385vault-security: the XSS checks asserted the escaped payload was absent from rendered text, which fails on correct escaping — assert instead that no script element, img or inline handler is ever created, and that GET_ENTRIES answers vault_locked once locked3 months agobd082b4a23c5playwright: point the specs at the list overlay — the top search bar is readOnly and only opens the list, so filling it or clicking new-entry from the vault stage could never work3 months agocce5d8227d4eextract the working vault setup into tests/helpers/vault.ts, which asserts it reached the unlocked vault instead of skipping creation silently; port lock-screen, entry-crud, settings, search, vault-security and vault-lifecycle onto it and drop the three assertion-free specs3 months ago9378234431eesync indicator light (pulsing green syncing / solid green healthy / red problem) plus persistent last-attempt reason in Settings and the topbar sync button (v4.2.10)3 months agode6976b06e68every terminating sync path reports a named SyncOutcome with device inventory, persisted last attempt, and [Peach sync] service-worker logs3 months ago7e3d43b00009match device revocation on the revoked long-term key, not just the self-asserted deviceId, so a revoked device cannot return under a fresh id (v4.2.9)3 months ago602463675e06record that the old feedback key had no account behind it, so a 200 success was never evidence of delivery, and narrow B5 to June confirming the test email arrived3 months ago89e76b54a2b7point feedback at the Web3Forms account that actually exists — the previous key was never set up, which is why every submission was accepted and nothing was ever delivered (v4.2.8)3 months ago70f1095eb4c1rewrite the consolidated queue around what actually blocks sync, and record the feedback diagnosis, the website rewrite, and the kapt trick that finds an unattributed Kotlin error3 months ago478a839aacaedelete the SUBMIT_FEEDBACK handler that returned ok while sending nothing, and the 261 lines of pairing-code CSS no component has referenced since the code-entry surface was removed (v4.2.7)3 months agoc8a0fc89e74dcorrect the feedback queue item: the extension's Web3Forms path works, only Android has no endpoint, and the SUBMIT_FEEDBACK handler returns ok while sending nothing3 months ago9369069f7f73record the settings-UX and relay-surfacing session, the adoption relabelling bug the fail-closed gate exposed, the adopt-screen deviation and why, and queue the feedback-backend worker without its credentials3 months ago26cd2586ed62stop the flex column stealing the bird stage's height to fit what is below it, and pay for the two new rows on the invitation screen by moving what the code contains onto the text view where the string is actually visible (v4.2.6)3 months agoc626a5aa8656put 'Show a code instead' under the QR: the same invitation as selectable text with a copy button, for a camera that will not focus (v4.2.5)3 months ago25d58a4fe204surface the relay choice on the invitation screen as a quiet change link that rebuilds the code, and say plainly on the adopt screen that the scanned code carries the relay rather than offering a choice it would overwrite (v4.2.4)3 months ago2fdc9c8169eaextract the three-state relay choice into one SyncModeSelector so Settings and the pairing surfaces cannot drift: exact disclosure line, radio-group semantics, and an empty private URL field that says sync is paused instead of quietly using the public relay (v4.2.3)3 months agoa5b058442cd7fail closed when Private relay is chosen with no URL: one relayInForce gate for sync and pairing, and stop pushing the public relay to peers under a private label (v4.2.2)3 months ago
details
Peach
A free, open source, local-first password manager for Chrome, Firefox, and Android.
Peach encrypts your vault on your device. No hosted vault, subscription, or account is required to use it.
Features
- Passwords, cards, and secure notes — keep your private data together in one encrypted vault
- Inline autofill — fill and save credentials without leaving the page
- TOTP built in — generate two-factor codes without a separate authenticator
- Password health — find weak, reused, and exposed passwords
- Portable backups — export and restore with PeachScript or a
.peachfile
Peach Pro adds:
- Peach Sync — end-to-end encrypted sync across paired devices
- Passkeys — save and use passkeys in Chrome and Firefox
- Peach Codex — print an encrypted, scannable backup of your vault
- Advanced vault health, Canary Entries, and duress tools
See the Peach website for current availability and Pro details.
Install
Open Source
Peach is released under the GPL v3. This repository contains Peach's Chrome and Firefox browser extensions. Android is maintained separately.
The source is hosted on Kepr, Asha Software's version control platform.
Security
Vault data is encrypted with AES-256-GCM and protected by Argon2id key derivation. Peach Sync authenticates paired devices and encrypts data in transit.
Implementation details live alongside the code:
Building
bun install --frozen-lockfile
bun run build
Builds are written to dist-chrome/ and dist-firefox/.
Built by Asha Software · [email protected]