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

@pome-sh/cli

v0.3.0

Published

Digital-twin testing for AI agents — run scenarios against resettable local or hosted twins and record tool-call traces for evaluation on pome.sh.

Readme

Pome CLI

The pome command runs AI-agent scenarios against resettable digital twins of real SaaS APIs (GitHub, Stripe, …), captures the trace, and gets a verdict from Pome cloud.

The CLI is capture-only: it records raw traces and never scores, judges, or correlates locally. A verdict comes only from the cloud — a hosted pome run prints it to the terminal and records it to the dashboard, and pome eval <run-dir> uploads a captured trace for a cloud verdict.

📚 Full documentation lives at docs.pome.sh. Run pome --help (or pome help <command>) for the CLI reference, and pome docs getting-started to open the canonical quickstart.

Install

npm install -g @pome-sh/cli
pome --help

Or run it without installing: npx @pome-sh/cli <command> — e.g. npx @pome-sh/cli twin start github boots a local GitHub twin with nothing but Node ≥ 24.

Quickstart

pome login                       # one-time; opens the dashboard to sign in
pome init                        # scaffolds scenarios/, examples/agents/, runs/, pome.config.json
pome register agent my-agent     # scopes runs to this project
pome run scenarios/01-bug-happy-path.md --agent "npx tsx examples/agents/scripted-triage-agent.ts"
pome inspect latest              # trace/audit view of the last run

To capture a trace without the cloud (self-host), then get a verdict later:

pome run --local scenarios/01-bug-happy-path.md   # captures a raw trace only — no verdict
pome eval runs/01-bug-happy-path/<run-id>         # uploads it for a cloud verdict

See docs.pome.sh for the scenario library, exit-code contract, authentication, the Stripe/Slack twins, and everything else.

Development

npm install
npm run typecheck
npm run build
npm test

The package publishes the pome binary from dist/src/cli/main.js.

Versioning — every behavior change ships with a bump

Any PR that touches cli/src/** must either add a changeset under cli/.changeset/ or bump cli/package.json directly; CI enforces this via scripts/check-cli-version-bump.sh. Preferred path: cd cli && npm run changeset.

License

Apache-2.0. See LICENSE.