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

zkwhistleblower

v0.0.4

Published

<p align="center"> <img src="./assets/logo.svg" alt="zkW logo" width="180" /> </p>

Readme

zkWhistleblower (TS SDK)

JavaScript/TypeScript helper package for generating inputs, proving, and verifying the zkWhistleblower Noir circuit.

Unstable Release Warning

This package is currently unstable and should be treated as pre-release software.

  • APIs may change without notice.
  • Build outputs and package exports may change between versions.
  • Proof formats must match verifier settings exactly (especially Honk keccak options).
  • Do not use this package in production systems without pinning exact versions and running full integration tests.

Requirements

  • Node.js 22+
  • pnpm (recommended) or yarn
  • Circuit artifacts generated in ../target (run make compile from repo root)

Install

pnpm install

Build

pnpm build

Watch mode:

pnpm dev

Output Targets

The package builds two ESM targets:

  • Node backend build: dist/node
  • Browser build: dist/browser

package.json exports are configured so Node and browser consumers resolve the correct bundle automatically.

Usage

import {
  ProofLeakProver,
  generateInputs,
  extractEmailAddresses,
  domainSequence,
  domainInputs,
} from "proof-leak-noir";

const prover = new ProofLeakProver("honk", 4);

const inputParams = {
  extractFrom: true,
  extractTo: true,
  maxHeadersLength: 1024,
  maxBodyLength: 1024,
};

// 1) Build zk-email base inputs from .eml content
const inputs = await generateInputs(emlBuffer, inputParams);

// 2) Build circuit-specific domain inputs
const parsed = extractEmailAddresses(emlBuffer.toString());
const from_domain_sequence = domainSequence(inputs.header.storage, parsed.from.address);
const to_domain_sequence = domainSequence(inputs.header.storage, parsed.to.address);

const plInputs = {
  ...inputs,
  from_domain_sequence,
  to_domain_sequence,
  domain: domainInputs(parsed.to.domain),
};

// 3) Prove and verify
const proof = await prover.fullProve(plInputs);
const ok = await prover.verify(proof);
console.log("verified:", ok);

await prover.destroy();

Testing

pnpm test

Important Notes

  • DKIM input generation depends on network DNS lookups. Offline or restricted-network environments may fail before proving.
  • For Honk proofs, proving/verifying options must match exactly.
  • If integrating with external verifiers, ensure the expected proofType, VK format, and public input count match your compiled circuit.