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

@hazae41/secp256k1-wasm

v2.0.0

Published

WebAssembly port of Secp256k1

Downloads

9

Readme

secp256k1.wasm

WebAssembly port of Secp256k1

npm install @hazae41/secp256k1-wasm
deno install jsr:@hazae41/secp256k1-wasm

📦 NPM📦 JSR

Features

  • Reproducible building
  • Pre-bundled and streamed
  • Zero-copy memory slices

Modules

  • k256

Algorithms

  • ECDSA over Secp256k1

Usage

import { secp256k1Wasm } from "@hazae41/secp256k1-wasm";

// Wait for WASM to load
await secp256k1Wasm.initBundled();

using hash = new secp256k1Wasm.Memory(crypto.getRandomValues(new Uint8Array(32)))

using keypair = new secp256k1Wasm.Secp256k1SigningKey()
using identity = keypair.verifying_key()

using signaturex = keypair.sign_prehash_recoverable(hash)
using signaturem = signaturex.to_bytes()
const signatureb = signaturem.bytes

const r = signatureb.subarray(0, 32)
const s = signatureb.subarray(32, 64)
const v = signatureb[64]

using identity2 = secp256k1Wasm.Secp256k1VerifyingKey.recover_from_prehash(hash, signaturex)

Building

Reproducible building

You can build the exact same bytecode using Docker

npm run compile

Then check that all the files are the same using npm diff

npm diff

If the output is empty then the bytecode is the same as the one I published on NPM.

Automated checks

Each time I release a new version on GitHub, the GitHub's CI clones the GitHub repository, reproduces the build, and throws an error if the NPM release is different. If a version is present on NPM but not on GitHub, do not use it!