Release 4.115.0
6 Nov 2026 · pinned package [email protected]
- Locker in the browser (
ov-locker.js,ov-locker.css; plan Q2; docs/locker.md). The owner: "completely encrypted on our end … decrypted on the client's end, so we don't have access to any of the user data."OVLocker.open(el, { bytes | url }): a locked item's card. A link lock opens with the key after#k=, and a link missing it says so. A password lock opens with its password, on the device. A people lock asks to unlock your locker, and someone not on the list is told so.OVLocker.setup(): make your locker. A passphrase with a strength meter, a 24-word recovery kit shown once and checked with two of its words, then the eight-word fingerprint. Network keeps the public keys, a self-signature and two password-locked envelopes of the private keys.OVLocker.unlock(): unlock with the passphrase or the recovery kit. "I lost both" starts a new locker (reset) after a plain warning.- Secrets stay in the tab's memory: never sent, never stored.
ov-locker-core.js:openvibe-sdk/locker0.86.0 for the browser, generated byscripts/build-locker-core.jsfrom the SDK's own files (WebCrypto only).- test/ov-locker-core.test.js makes the SDK's vectors again in a browser-only VM, with the same bytes, and crosses envelopes between the browser and Node.
- test/ov-locker-e2e-chrome.test.js uses the real crypto: make a locker, unlock it on a new device by passphrase and by recovery words, open what was locked for you, refuse what was not.
- openvibe-sdk devDependency 0.82.0 → 0.86.0.
PagesThe kit