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

@czirkeorg/pr-reviewer

v0.9.0

Published

Local app that reviews the PRs requested from your GitHub accounts with Claude Code, lets you edit the findings, and publishes the review.

Readme

PR Reviewer

Local app that lists the PRs where your GitHub accounts were asked to review, runs the review with Claude Code inside the local clone, lets you edit the findings and verdict, and publishes the review. After a review, you can talk to Claude about it on the same page: ask why a finding is there or point out what it missed, and Claude updates the summary, verdict, and findings. A published review that you are asked to review again shows as "Requested again", with whether the PR has new commits since.

Quick start

npx @czirkeorg/pr-reviewer

Open http://127.0.0.1:4317. If gh and Claude Code are logged in on your machine, there's nothing to set up: the app uses those logins, finds your clones under ~/projects, and reads Claude Code's project memory. Data lives in ~/.pr-reviewer.

Requires Node 20.11+. Environment variables: PORT (default 4317), DEFAULT_LANGUAGE (en or pt, default en), SCAN_ROOTS (comma-separated folders with your clones), DATA_DIR.

Run with Docker

docker run -d --name pr-reviewer -p 127.0.0.1:4317:4317 -v pr-reviewer-data:/data christianzirke/pr-reviewer

Open http://127.0.0.1:4317 and, in Settings:

  1. GitHub accounts: paste a token with the repo and read:org scopes (the output of gh auth token, or a new one). Add one per account.
  2. Claude access: run claude setup-token on your machine and paste the token it prints (an API key also works).
  3. Jira (optional): the site address, your e-mail, an API token, and the projects it serves. Add one per Jira site. The PR's task (found in the title, branch, or description) then goes into the review as its contract.

Without a local clone, the app fetches the PR code from GitHub, so Claude reads whole files and the repository's CLAUDE.md. Tokens stay in the pr-reviewer-data volume and never go back to the browser.

| Variable | Default | | |---|---|---| | DEFAULT_LANGUAGE | en | en or pt, until one is picked in the app | | CLAUDE_CODE_OAUTH_TOKEN, ANTHROPIC_API_KEY | | Claude access by env instead of the Settings page |

Keep the port bound to 127.0.0.1: the app posts reviews with your GitHub accounts.

Optional: your clones and project memory (Linux/WSL)

Mount Claude Code's folder and your clones, at the same path as on the host (Claude Code keys project memory by path). The app then reviews inside your clone, with its memory, and can use your gh and Claude Code logins instead of tokens:

docker run -d --name pr-reviewer -p 127.0.0.1:4317:4317 -v pr-reviewer-data:/data \
  -e SCAN_ROOTS=$HOME/projects \
  -v $HOME/projects:$HOME/projects \
  -v $HOME/.claude:/home/node/.claude -v $HOME/.claude.json:/home/node/.claude.json \
  -v $HOME/.config/gh:/home/node/.config/gh \
  christianzirke/pr-reviewer

The container runs as uid 1000; ~/.claude.json must exist before the first run.

Run from source

Requires Node 22.18+, gh, git, and claude logged in.

npm install
npm run dev     # http://127.0.0.1:4317, UI served by Vite
npm test
npm run check   # type-check

Compare review skills

npx @czirkeorg/pr-reviewer compare <owner>/<repo>#<N> [--as <account>] runs every reviewer listed in ~/.pr-reviewer/config.json (create it if it doesn't exist; without these settings the command prints what to add) on one PR, each in its own Claude process and in dry run (a guard hook denies any remote write, and any write outside the reviewer's folder), then writes the comparison. Nothing is posted: open the PR in the app, pick which review to start from (or check findings from the others), and publish as usual.

"compareDir": "~/projects/devoz/review-comparativo",
"compareModels": ["ozmap-1532/comparativo.md", "ozmap-1530/comparativo.md"],
"reviewers": [
  { "id": "base", "source": { "type": "prompt" } },
  { "id": "B1", "source": { "type": "github", "repo": "ozmap/skill-sandox", "ref": "a8fa73a", "path": ".claude/skills/oz-code-review" } },
  { "id": "B2", "source": { "type": "github", "repo": "ozmap/skill-sandox", "ref": "task/SQMAP-325-padronizar-skill-de-2", "path": ".claude/skills/oz-code-review" } }
]

Sources: prompt (the built-in reviewer), plugin ({ "skill": "dev:review-pr", "args": "nível médio" }), dir ({ "path": "..." }) and github (pinned by sha in <compareDir>/_skill/<name>@<sha7>/). Each reviewer writes review.json, report.md, meta.json (time, cost, tokens) and its own artifacts to <compareDir>/<repo>-<N>/r<k>/<id>/; a separate agent appends round k to <repo>-<N>/comparativo.md and updates the PR's row in <compareDir>/README.md. From source: DATA_DIR=~/.pr-reviewer node server/compare-cli.ts ozmap/ozmap#1532 --as christianzirke.

Image: christianzirke/pr-reviewer. Build it locally with docker build -t christianzirke/pr-reviewer:latest .