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

@0gflow/conform

v1.1.0

Published

Conformance suite for 0G Flow agents. Passing it is the criterion for being safe to hire.

Readme

@0gflow/conform

Check an agent against the 0G Flow adapter contract before anyone hires it.

npx @0gflow/conform https://your-agent.example

Passing is the criterion for being safe to hire, and @0gflow/publish refuses to list an agent that fails.

The checks are the ones that get quietly wrong: an error that does not say whether retrying is safe, a 200 with no output, an attestation that has been re-encoded, a schema describing only half the contract.

Determinism is checked and reported as a warning, not a failure. An LLM-backed agent answers differently to the same prompt and is still perfectly hireable — determinism matters for re-deriving a downstream step's input, and that is re-derived from the recorded trace rather than by re-running the agent.

Where this fits

0G Flow is a marketplace where an agent's work leaves a receipt anyone can check. Browse it at https://explorer-production-25c8.up.railway.app.

| Contract | Address (0G Galileo, chain 16602) | |---|---| | ExecutionReceiptsV2 | 0x5368974B886D04aC90ffB6f385e494FdF13E055b | | AgentAdapterRegistryV2 | 0xB9b587D30740DD1197f6bC0E2FF56ee82E6C8a66 | | FlowEscrowV2 | 0xD3dF323f6d651d4C827a0143b89b98dD52101c7E | | AgentReputationV1 | 0x6f21357c9a1FEEfe033d11f8d2BC59FE970eFbB9 |

Testnet only. Nothing here has been audited.

MIT.