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

wickra-proof-wasm

v0.2.0

Published

WebAssembly bindings for wickra-proof — the deterministic Proof-of-Backtest core in the browser.

Readme

CI codecov npm License: MIT OR Apache-2.0

Wickra Proof — WASM


Proof-of-Backtest. Turn a (spec, data) pair into a deterministic backtest report and a canonical blake3 hash that anyone can recompute byte-for-byte in ten languages — for WASM. npm install wickra-proof-wasm — pure WebAssembly, runs anywhere a modern JS engine does.

WASM bindings for the wickra-proof deterministic Proof-of-Backtest core, compiled to WebAssembly with wasm-bindgen.

Create a stateless Prover, drive it with a command JSON (prove, verify, canonicalize, version) and read back the response JSON — the same protocol as every other binding, running in the browser.

The core is built with --no-default-features, so the backtest engine runs sequentially (no rayon thread pool in the browser sandbox) and the report and its blake3 hash are byte-identical to the native ones — the exact cross-language golden check.

Install

npm install wickra-proof-wasm

Building from this repository (contributors)

wasm-pack build --target web

This emits pkg/ with the .wasm module and JS glue.

Quick start

import init, { Prover, version } from "wickra-proof-wasm";

await init();

const prover = new Prover();
const proof = JSON.parse(
  prover.command(JSON.stringify({ cmd: "prove", spec, data })),
);
// proof.report_hash / proof.inputs_hash are 64-hex blake3 digests, identical
// to the native CLI for the same (spec, data).

const verdict = JSON.parse(
  prover.command(JSON.stringify({ cmd: "verify", proof, spec, data })),
);
// { ok: true, valid: true }

console.log(version()); // the library version

Commands

| Command | Payload | Response | | -------------- | --------------------------- | ----------------------------------------------- | | prove | { spec, data } | { report, inputs_hash, report_hash, engine_version } | | verify | { proof, spec, data } | { ok: true, valid: bool } | | canonicalize | { value } | { ok: true, canonical } | | version | — | { engine_version } |

Errors are reported in-band as { "ok": false, "error": "…" }.

Benchmark

Every binding forwards to the same data-driven Rust core, so what this one adds is the call overhead of wasm-bindgen, not a different result. The core's throughput is measured by the repository's benchmark suite and the nightly bench.yml run; the numbers, the machine and how to reproduce them are in the repository BENCHMARKS.md.

Documentation

The full guide, the spec reference and the API documentation live in the main repository and the documentation site:

Wickra Proof ships native bindings for Python, Node.js, WASM and Rust, plus a C ABI hub that any C-capable language (C, C++, C#, Go, Java, R) links against — all forwarding to the same data-driven, unsafe-forbidden Rust core.

Security

Found a security issue? Please don't open a public issue. Report it privately via the repository's Security tab ("Report a vulnerability") or email [email protected] with a subject line starting [wickra security]. Full policy: https://github.com/wickra-lib/wickra-proof/blob/main/SECURITY.md.

Disclaimer

wickra-proof is research and engineering tooling, not financial advice. A proof attests only that a given report is the deterministic result of a given spec over given data — it makes no claim about the quality, profitability or future performance of any strategy. Trading carries risk; you are responsible for your own decisions.

License

Licensed under either of Apache-2.0 or MIT at your option.