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

@ethproofs/pico-wasm-stark-verifier

v0.1.7

Published

WASM wrapper for Pico STARK verifier - verify STARK proofs in browsers and Node.js

Readme

Pico Wasm Stark Verifier

WebAssembly bindings for the Pico STARK verifier.

Overview

This module compiles the verify function from pico-vm's CombineProver to WebAssembly, allowing STARK proof verification in web browsers and Node.js environments.

For the Pico STARK verifier to work, the env variable VK_VERIFICATION needs be set to false, but this is challenging when compiling to WASM. Therefore, as a temporary solution, this pkg uses a fork of Pico which bypasses a vk_verification_enabled check in the verify function and assumes it is disabled.

Usage

Installation

npm install @ethproofs/pico-wasm-stark-verifier

React Integration

import init, { main, verify_stark } from '@ethproofs/pico-wasm-stark-verifier';

await init(); // Initialize WASM (if needed)
main(); // Initialize panic hook

// Verify a Pico proof (single GPU)
const isValid = verify_stark('Pico', proofBytes, vkBytes);

// Verify a Pico Prism proof (multi GPUs)
const isValid = verify_stark('PicoPrism', proofBytes, vkBytes);

For complete React integration examples, see REACT_INTEGRATION.md.

Node.js Usage

const { main, verify_stark } = require('@ethproofs/pico-wasm-stark-verifier');

// The Node.js version initializes automatically

main(); // Initialize panic hook
const result = verify_stark('PicoPrism', proofBytes, vkBytes);

Testing

Installation

npm install

Prerequisites

Building

# Build for all targets
npm run build:all

Node.js Example

npm run test:node

This runs the Node.js example that loads proof and verification key files from the filesystem and verifies them using the KoalaBear field configuration.

Browser Example

npm run test

This starts a local HTTP server at http://localhost:8080 with a browser example that demonstrates:

  • Loading the WASM module in a browser environment
  • File upload interface for proof and verification key files
  • Interactive STARK proof verification
  • Performance metrics and detailed logging
  • Error handling and user feedback

The browser example provides a complete UI for testing the WASM verifier with drag-and-drop file selection and real-time verification results.

Note: The browser example requires files to be served over HTTP due to WASM CORS restrictions. The included server script handles this automatically.