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

@siteverb/runner

v0.1.1

Published

Deterministic real-browser runner for Siteverb WebMCP journey contracts.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

rohanprasadofficialrohanprasadofficial

Keywords

webmcpbrowser-testingpuppeteergithub-actions

Readme

@siteverb/runner

Deterministic real-browser execution for siteverb.webmcp.json contracts.

npx @siteverb/runner \
  --contract siteverb.webmcp.json \
  --url http://127.0.0.1:3000 \
  --output .siteverb/report.json

The runner launches a named Chrome channel with WebMCP enabled, opens a fresh page for each journey, refreshes the native tool inventory before every step, executes through Puppeteer's official page.webmcp API, checks bounded result/URL/DOM postconditions, attempts cleanup, and writes a versioned evidence report.

Targets must be absolute HTTP(S) URLs. Per-navigation, tool, and postcondition timeouts are bounded to 1-600,000 milliseconds and validated with journey/profile filters before browser acquisition.

Journey steps fail fast. Cleanup is best-effort: every declared cleanup step is attempted even when an earlier one fails, and any cleanup failure still fails the journey.

Add --profile chatgpt-site-tools-2026-08-26 to include a dated documented compatibility assessment. This never upgrades documented behavior to real-client evidence.

Mutating tools do not run unless --allow-mutations is present. A stable tool ID listed in a journey's requireHumanBefore policy also requires --approve <stable-id>. Use these flags only against an explicitly approved local, preview, or seeded test target.

The default report excludes prompts, inputs, tool outputs, DOM snapshots, cookies, and credentials. It records browser provenance, step status, duration, and Siteverb-generated failure categories. The persisted target is reduced to its origin; path, query, fragment, and URL credentials are omitted. --include-error-details opts a local run into bounded page-provided error messages; do not use it for shared CI artifacts unless those messages are independently redacted.