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

nitpick-qa

v0.1.0

Published

Nitpick — independent adversarial QA agent for AI-generated (and human) code. Professionally picky.

Readme

Nitpick

Nitpick is an agent-agnostic, BYOK QA agent that acts as an independent adversarial tester for code produced by AI coding agents (Claude Code, Cursor, Codex, Aider, …) or humans. It plans and executes tests, then emits a machine-readable Verdict (QVP) that any coding agent can consume in a fix→retest loop. Findings are called nits.

Install

npm install -g nitpick-qa   # provides the `nit` CLI

Requires Node ≥ 20. Docker is recommended (sandboxed test execution); without it Nitpick falls back to a restricted subprocess and marks verdict confidence as degraded.

Quick start

cd your-project
nit init        # detect stack, scaffold .nit/
nit plan        # see what Nitpick intends to run
nit run         # execute + emit verdict (exit code mirrors it)
nit verdict     # re-print the last verdict (--json for QVP)

Exit codes: 0 pass / pass-with-warnings, 1 fail, 2 inconclusive.

CLI

nit init                      # detect stack, scaffold .nit/
nit plan [--diff <base>]      # produce/print test plan
nit run [--only dims] [--diff <base>] [--smoke] [--json]
nit verdict [--json|--md]     # print last verdict
nit repro <nit-id>            # re-run a finding's exact repro
nit corpus [list|run|export]  # regression bug corpus
nit baseline update perf      # accept new perf baselines
nit mcp                       # start MCP server (stdio)
nit ci                        # CI-optimized: run + GitHub annotations
nit config                    # print effective config + hash

MCP

Register nit mcp as a stdio MCP server to give any agent the tools qa_plan, qa_run, qa_verdict, qa_repro, qa_corpus_search, and qa_await_fix (L3 loop handshake), plus nitpick://verdict/latest and nitpick://plan/latest resources. Example (Claude Code):

claude mcp add nitpick -- nit mcp

BYOK models

Configure in .nit/config.yaml — any Anthropic or OpenAI-compatible endpoint (OpenRouter, Ollama, vLLM, LM Studio). Keys are read from env vars only and never written to disk or verdicts. Without a configured model, adjudication falls back to deterministic heuristics.

models:
  judge: { provider: anthropic, model: claude-sonnet-5, api_key_env: ANTHROPIC_API_KEY }
  # worker: { provider: openai-compatible, base_url: http://localhost:11434/v1, model: qwen2.5-coder }
budget: { max_tokens_per_run: 500000, max_usd_per_run: 3.0 }

Autonomy levels

| Level | Behavior | |---|---| | L0 | Observe: runs and reports, never fails a build | | L1 | Plan-approval: interactive sign-off before execution | | L2 | Autonomous (default): plans, executes, gates | | L3 | Loop: enables the qa_await_fix fix→retest handshake |

Status / roadmap

This is M0 — the walking skeleton: stack ingest, existing jest/vitest/pytest suites executed in a sandbox, QVP verdicts with exit codes, CLI + MCP frontends, BYOK router (Anthropic + OpenAI-compatible), autonomy levels, corpus replay plumbing.

Coming next: M1 contract extraction + black-box test generation + bug corpus distillation; M2 integration/system/security layers + risk graph; M3 performance baselines, mutation spot-checks, usability audits.

License

Apache-2.0 — see LICENSE. The "Nitpick" name and logo are trademarks of the project owner; see TRADEMARK.md.