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

@zkpoc/broker

v0.1.0

Published

Shard queue, tier-aware sizing, redundancy consensus and audit sampling for consented browser compute

Readme

@zkpoc/broker

Shard model, tier-aware sizing, commit-then-challenge verification, redundancy consensus, stake-derived audit, and a credit ledger — the multi-client verification layer for consented browser compute. Splits into two structurally separate pipelines, deliberately not sharing a verification or reward path:

  • Barter — crowdsourced compute, a worker paid for confirmed work.
  • Challenge — anti-bot proof-of-work, useful work substituted into the slot hashcash-style widgets (Cloudflare Turnstile, Anubis, ALTCHA...) occupy today. See @zkpoc/challenge for the client-side solver.

Part of ZK-PoC, a consent-governed, verifiable browser-compute project. Zero runtime dependencies.

import {
  LAPTOP_IGPU, chooseShardSize,
  issueChallenge, resolveChallenge, ChallengeOutcome,
} from '@zkpoc/broker';

// Server side: issue a challenge sized for ~2s of GPU compute on a
// measured device tier.
const { shard } = issueChallenge(LAPTOP_IGPU, { targetWallSeconds: 2 });
// ...send shard.toJSON() to the client, which solves it (@zkpoc/challenge)...

// Then verify the response:
const { outcome } = await resolveChallenge(shard, submittedResult, {});
if (outcome === ChallengeOutcome.ADMIT) proceed();

Why commit-then-challenge

An earlier design derived the verification challenge from public shard data alone, which let a worker compute just the checked points and skip the real O(n³) computation entirely. The fix: a worker Merkle-commits every output row first, and the challenge is derived from that root via Fiat-Shamir — so a valid root costs the real computation, full stop. See ADR-0011.

What's in here

| Module | What it does | | --- | --- | | tiers | Device-tier shard sizing from measured constants; refuses to guess for an unmeasured tier | | shard, merkle | Deterministic-but-fresh shard inputs, row-level Merkle commitment, Fiat-Shamir challenge derivation | | queue | Lease-based multi-worker assignment, replica independence | | consensus | Per-submission gate plus majority/dispute tally | | audit, ledger | Stake-derived audit rate (an economic inspection game, not fixed sampling), stake/reward/slash | | challenge | The anti-bot single-submission protocol (issue/resolve), deliberately not built on the barter pipeline above |

Status

Experimental — API surface may still change. 170 tests.

License

MIT OR Apache-2.0.