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

@clipboard-health/tribunal

v1.2.21

Published

Structured second opinions from advocate, skeptic, analyst, and deliberator LLM perspectives.

Readme

Tribunal CLI

tribunal gets a structured second opinion from advocate, skeptic, and analyst LLM perspectives, then synthesizes the result with a deliberator model.

Run with API key environment variables already present:

npm --workspace @clipboard-health/tribunal run dev -- "Should we migrate?" --verbose

For local defaults, copy the checked-in example to a gitignored root config:

cp tribunal.config.example.json tribunal.config.json

The CLI searches for tribunal.config.json from the current working directory upward. Config values are defaults only; explicit CLI flags still take precedence.

{
  "apiKeys": {
    "anthropic": "op://Private/ANTHROPIC_API_KEY/credential",
    "googleGenerativeAi": "op://Private/GOOGLE_GENERATIVE_AI_API_KEY/credential",
    "openai": "op://Private/OPENAI_API_KEY/credential"
  },
  "models": {
    "advocate": "anthropic:claude-opus-4-7",
    "skeptic": "openai:gpt-5.5",
    "analyst": "google:gemini-3.1-pro-preview",
    "deliberator": "openai:gpt-5.5"
  },
  "reasoning": {
    "advocate": "max",
    "skeptic": "xhigh",
    "analyst": "high",
    "deliberator": "xhigh"
  },
  "outputFormat": "text",
  "showPerspectives": false,
  "saveIntermediates": true
}

--verbose writes progress to stderr, including per-role start, finish, and failure lines, plus a dot every five seconds while model calls are in flight.

Each run writes durable intermediate snapshots to .tribunal/runs/<timestamp>.json by default. The file is updated as each role starts, finishes, or fails, so completed perspective outputs are preserved even when a later model call fails. Use --save-intermediates <path> to choose a specific file, or --no-save-intermediates to disable snapshots.

After a successful run, an HTML report is written to .tribunal/reports/<timestamp>.html and opened in your default browser. The report shows the deliberator's verdict, recommendation, and confidence at the top, with each perspective (advocate, skeptic, analyst) as a collapsible accordion below. Override the path with --html <path>, skip opening with --no-open, or disable the report entirely with --no-html.

Override model reasoning or thinking levels per role:

npm --workspace @clipboard-health/tribunal run dev -- "Should we migrate?" \
  --model advocate=anthropic:claude-opus-4-7 \
  --model skeptic=openai:gpt-5.5-pro \
  --model analyst=google:gemini-3.1-pro-preview \
  --deliberator openai:gpt-5.5-pro \
  --reasoning advocate=max \
  --reasoning skeptic=xhigh \
  --reasoning analyst=high \
  --reasoning deliberator=xhigh

Reasoning levels are mapped to each provider's AI SDK options. OpenAI supports none, minimal, low, medium, high, and xhigh; Google supports minimal, low, medium, and high; Anthropic supports low, medium, high, xhigh, and max.

Run through 1Password without writing secret values to disk:

npm --workspace @clipboard-health/tribunal run dev:op -- "Should we migrate?"

When apiKeys are present in tribunal.config.json, tribunal-op passes those 1Password references to op run, which resolves them in the child process environment at runtime.