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

recon-registry

v0.3.1

Published

Package a Foundry project into a single self-contained fuzzing harness/mock and publish it to the Recon contract registry, deployable by name from the operator.

Readme

recon-registry

A community catalog of single self-contained fuzzing harnesses and mocks, deployable by name into the Recon operator. Package a whole protocol (or a standalone tester like an ERC-4626 vault or a weird ERC-20) into one self-contained contract whose constructor stands the project up — then anyone can fuzz it.

operator (Rust)                 recon-registry (this repo)              you (a Foundry project)
  deploy_from_registry(name) ──▶  entries/<name>.json  ◀── PR ──  npx recon-registry pack/publish

Use an entry (consumer)

From the operator: deploy_from_registry("ERC4626Tester", as_actor: true) — fetches the entry and stands the project up at a deterministic address. Browse: npx recon-registry list.

Contribute an entry (author)

In your Foundry project:

npx recon-registry init       # scaffold recon-registry.toml + registry/Harness.sol + Rvm.sol
# write your harness (its constructor news+wires the whole project; see registry/Harness.sol)
npx recon-registry pack       # forge build + extract → recon-registry-out/<name>.json
npx recon-registry publish    # write token → auto-PR; else opens a prefilled issue (one Ctrl+V)

Model (intentionally simple)

  • One entry = one contract. A "project" is a single self-contained Setup-style harness whose creation bytecode embeds and deploys its deps. No multi-contract manifests, no dependency ordering.
  • Entry schema (schema/entry.schema.json): name, description, tags, abi, creationBytecode, source, solc. Source is inlined (humans + the LLM read behavior); no heavy provenance.
  • Formats: manifest = TOML (recon-registry.toml, human-edited); entries = JSON (entries/*.json, machine-generated). Same split as foundry.tomlout/*.json.

Trust = reproducibility, enforced in CI

On every PR, CI recompiles the entry's source with its solc and asserts the bytecode matches, validates the schema, and smoke-deploys. On merge to main, registry.json is rebuilt and the entry is immediately available to the operator (merge = publish).

Layout

entries/*.json   published entries (machine-generated)
src/*.sol        the harness/mock sources (for browsing + CI recompile)
schema/          the entry JSON schema
registry.json    the catalog index (CI-generated on merge)

See CONTRIBUTING.md for the full author guide.