VaultKeepR/vaultkeepr-public
vaultkeepr-public is the MIT-licensed repository behind VaultKeepR, a zero-knowledge password manager. It holds 15 SDK packages published to npm under @vaultkeepr and Solidity contracts on Base L2 that anchor vault locations, recovery fragments and digital legacy, tested with Foundry. Encryption is XChaCha20-Poly1305 with Argon2id (t=3, m=64 MiB, p=4), and docs/THREAT_MODEL.md covers assets, adversaries and trust boundaries. Clients stay in a private repository.
What it is
vaultkeepr-public is the MIT-licensed part of VaultKeepR, a zero-knowledge password manager. It holds the SDK packages shared by every VaultKeepR client and the Solidity contracts on Base L2. The web app, browser extension and iOS/Android apps are in a private repository, so only the building blocks can be audited or reused. The page's package table was not in the fetched text, so individual package names beyond @vaultkeepr/core are not listed here.
How it works
The page makes these design claims. It does not show the code behind them.
- The master password never leaves the device.
- Encryption is XChaCha20-Poly1305 AEAD with Argon2id key derivation (t=3, m=64 MiB, p=4).
- Ciphers, curves and hashes come from
@noble/*. Ethereum types and clients come fromviem. - An on-device small language model (SLM) engine does auto-tagging and breach summaries, and the page says no vault data reaches a server.
- Keys, CIDs and addresses are redacted at the logger level.
docs/THREAT_MODEL.mddocuments assets, adversaries, trust boundaries and accepted limitations. The accepted limitations are the part to read before relying on the design.
Preconditions / Affected
Building needs Node.js 20+ and pnpm 9+. Foundry is needed only for the contracts. The workspace uses Turbo (turbo.json) and pnpm workspaces.
What to do
To use the SDK:
npm install @vaultkeepr/coreTo build and test the workspace:
pnpm install
pnpm build
pnpm testTo test the contracts:
cd contracts
forge install
forge testReport vulnerabilities by following SECURITY.md.
Caveats
- SDK packages version independently and are published per package with
pnpm publish. Check each package's npm badge for its current version. - Repository tags (vX.Y.Z) cover the full workspace and client artifacts. Only client releases (browser extensions, mobile) are minisign-signed. The page does not say the npm packages are signed.
- The clients are private, so the page gives no way to check that they use these packages as described.
Organisations named here
- Argon2id
- XChaCha20-Poly1305
Technologies named here
- XChaCha20-Poly1305 AEAD
- Argon2id
- @noble/*
- viem
- On-device SLM engine
- minisign
- docs/THREAT_MODEL.md
- Solidity
- Foundry
- npm
- Base
- VaultKeepR
Techniques named here
- Zero-knowledge design
- Logger-level redaction of keys, CIDs and addresses
Related in Identity & Access
Education Under Attack: The Pattern Behind Recent University Breaches
Next-Gen Phishing Tactics Users Aren’t Ready For | Huntress
.png)
Google API keys keep working after you delete them
