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

quacktionable

v0.1.0

Published

Rubber Duck Tribunal: cross-examine bugs and vote on root cause.

Downloads

99

Readme

quacktionable banner

quacktionable is a playful terminal tool that helps you explain a bug, survive cross-examination by judge ducks, and get a voted root-cause verdict.

It is built around GitHub Copilot CLI as the reasoning engine.

Why this is useful

Most debugging stalls because we lock onto our first theory too early.

quacktionable forces structured skepticism:

  • take your bug narrative,
  • challenge it from multiple technical personas,
  • and produce a final, confidence-scored quackdict.

Features

  • Interactive intake mode with branded splash UI: quack report
  • Fast sample run: quack analyze --example
  • Flexible inputs: inline text, bug file, logs, and code paths
  • Live terminal progress animation while the tribunal is thinking
  • Terminal-friendly and JSON output modes
  • Copilot CLI health check with quack doctor

Requirements

  • Node.js >=18.18
  • GitHub Copilot CLI installed and authenticated

Install

npm install -g quacktionable

If you prefer npx (no global install):

npx quacktionable doctor

Quick start

quack doctor
quack report

Or run a one-command demo:

quack analyze --example

Local development

npm install
npm run build
npm link

Command reference

  • quack doctor — verifies Copilot CLI availability and prompt roundtrip
  • quack report — interactive guided bug intake + analysis
  • quack analyze --example — run with built-in sample bug/logs
  • quack analyze --bug "..." --log ... --path "a.ts,b.ts" — explicit inputs
  • quack analyze --bug-file bug.txt --log app.log — file-first workflow
  • quack analyze --json — JSON output for scripts/automation

Analyze flags

  • --example: auto-loads examples/bug.txt and examples/logs.txt
  • --bug: bug narrative text
  • --bug-file: path to bug narrative file
  • --log: raw log text or a log file path
  • --paths / --path: comma-separated code paths for extra context
  • --rounds: tribunal rounds per duck (1-5, default 2)
  • --json: emit machine-readable JSON only

What users see in terminal

🦆⚖️ Rubber Duck Tribunal (Court is now in session)
🎭 Opening statement: no bug survives cross-examination.
🆔 Session: 5a077c56-b0fe-4f18-a26e-1a7408d56273
🤖 Engine: gpt-5

📝 Bug Tale
- 🐛 Users intermittently get a 500 error...

🗳️ Judge Duck Votes
- 🦆 Detective Quackson: ...

🏛️ Final Quackdict
- 🎯 root cause: ...
- 🔥 confidence: 92%

Architecture

  • Input parsing (--bug, --bug-file, stdin, --log, --path[s])
  • Evidence bundling + signal extraction from logs
  • Copilot CLI cross-exam prompt + per-duck judgment prompts
  • Vote aggregation and confidence scoring
  • Pretty terminal renderer + JSON renderer

Development

npm run lint
npm run build
npm run test