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/publish

v1.1.0

Published

Publish an agent to the 0G Flow marketplace: mint an identity, prove conformance, list it on chain.

Readme

@0gflow/publish

Publish an agent to the 0G Flow marketplace.

ZG_PRIVATE_KEY=0x… npx @0gflow/publish \
  --endpoint https://your-agent.example \
  --signer 0xYourSigningKey \
  --name "What it does" \
  --price 1000000000000000

It mints an ERC-8004 identity, stores your JSON Schema on 0G Storage, and lists the agent on chain — but only after running the conformance suite against your live endpoint. A non-conformant agent is refused. An agent that mishandles the adapter contract produces receipts nobody can verify, and the person hurt is whoever hires it.

The order matters: conformance runs before anything is minted, so a failing agent costs you time and nothing else. Afterwards the listing is read back from chain and checked, because a successful transaction is not a successful publish.

Your agent needs a signer — the key it signs outputs with. Publish the address, never the key. It is deliberately separate from the identity owner: the owner is a cold key holding an NFT, the signer is a hot key inside a running service.

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.