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

@anon-rpc/harness-core

v0.4.0

Published

anon-rpc harness internals that do not depend on the platform: spec types, the call and log queues, the specifier read and hash check, and plain-value copying.

Readme

@anon-rpc/harness-core

The parts of an anon-rpc harness that are about the specification rather than about where the harness runs. Each harness — browser, browser extension, Node — wraps these in its own transport and isolation; sharing them is what keeps the harnesses agreeing.

Tracks the anon-rpc specification version 0.4.0. (The package version is kept >= that spec version.)

  • Spec types (@anon-rpc/harness-core/spec-types) — the §5 and §7–§13 type surface. Worker templates keep their own copy, so a worker builds with no harness dependency.
  • readSpecifier / fetchAndVerifyBundle (§4) — the specifier read through a bootstrap provider, the resolver fetch, and the keccak256 check. Entry kinds that need a transport, such as kps:, are passed in as a ResolverKind by a harness that has one; without it they are ignored, as §4.1 requires.
  • CallQueue (§8) — ordered, no-drop, one-at-a-time inbound calls.
  • LogQueue (§13.1) — ordered, bounded log retention.
  • copyPlainValue, encodePlain / decodePlain (§9.4) — copying plain values, and carrying them across a boundary that only takes JSON.
  • copyForwardedEntries (§9.1) — the fetch-init entries forwarded to the worker, copied at call time. Every harness calls it synchronously in its fetch, before anything is awaited.
  • RpcError / serializeError (§12) — errors that keep name and code across a boundary.

This is an implementation dependency of the harnesses, not something a wallet or a worker needs to install.

License

MIT