npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@nexys/zk-store

v0.1.13

Published

Browser client for zk-store: zero-knowledge encrypted file storage. Files are encrypted before they leave the device.

Readme

@nexys/zk-store

Browser client for ZK Store: zero-knowledge encrypted file storage. Files are encrypted in the browser before they leave it; the server only stores ciphertext and wrapped keys.

Use it to build a web app on zk.nexys.io with no backend of your own. API reference: https://zk.nexys.io/docs.

npm install @nexys/zk-store

Quick start

import {
  configure,
  ensureCryptoReady,
  createVault,
  unlockWithRecoveryPhrase,
} from "@nexys/zk-store";

configure({ baseUrl: "https://zk.nexys.io" });    // the default; optional
await ensureCryptoReady();                         // loads the WASM crypto

// A new vault. Show the phrase to the user: it is the only way back in.
const { vault, recoveryPhrase } = await createVault();

const id = await vault.upload("notes.txt", new TextEncoder().encode("hello"));
console.log(await vault.listFiles()); // [{ uuid, name, size, uploaded }]

// Later, or on another device:
const again = await unlockWithRecoveryPhrase(recoveryPhrase);
const { name, data } = await again.download(id); // data: ArrayBuffer
await again.delete(id);
again.lock();

upload takes an ArrayBuffer, a Uint8Array or a Blob (a File from an <input type="file"> works as is).

Sign in with ZK Store

Let users sign in with the ZK Store account and passkey they already have, like an SSO redirect: no new passkey, no new key, every browser.

// On page load:
const vault = await handleSignInRedirect(); // Vault after the redirect back, else null

// On your "Sign in with ZK Store" button:
await signInWithZkStore({ appName: "Acme Notes" }); // goes to zk.nexys.io and back

On zk.nexys.io the user signs in and approves your site. They come back to the same page, and handleSignInRedirect() returns their vault. The vault key travels only in the URL fragment (never sent to a server), encrypted to a one-time key that exists only in your tab.

Using it from your site

zk.nexys.io accepts calls from any website (CORS), so your app can be frontend-only. That is safe: no auth is in cookies, and every call needs a token that only a holder of the vault key can get.

Passkeys work from any HTTPS site: pass the options from registerOptions() / authenticateOptions() to navigator.credentials unchanged. zk.nexys.io names your own domain as the relying party, so your site gets passkeys of its own, in every browser, that no other site can use. The recovery-phrase flow above works from any site too.

Loading the WASM

ensureCryptoReady() with no argument fetches zk_store_crypto_bg.wasm from next to @nexys/zk-store-crypto's JS. Vite and webpack 5 copy that file for you. With other bundlers, serve the file yourself (it is in node_modules/@nexys/zk-store-crypto/pkg/) and pass its URL:

await ensureCryptoReady("/zk_store_crypto_bg.wasm");

On a server runtime (Bun, Node, Deno), pass the bytes instead.

Lower-level API

Everything the ZK Store web app uses is exported too:

  • Crypto: generateKey, wrapKey/unwrapKey, encrypt/decrypt, deriveKey, deriveRecoveryKey, generateRecoveryPhrase, …
  • API calls: openVault, getBlob/putBlob/deleteBlob, invites, passkey ceremonies, subscriptions, and client, the typed openapi-fetch client.
  • File list: loadTree, updateTree (retries on conflicts with other devices), loadFileList.
  • Sharing: createShare, joinShare, downloadSharedFile, … for file and folder links.

The server's API is documented at /docs on any ZK Store server.

License

MIT