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

pyor-review

v0.5.2

Published

Open your working git changes as an AI-reviewed local pre-PR review in the Pyor desktop app. Works with any coding agent.

Readme

pyor-cli

Agent tooling for Pyor, the native home for GitHub code review. Works with Claude Code, Codex, Cursor, and any coding agent.

Open your working changes as a local pre-PR review in the Pyor desktop app, before a PR exists. /pyor:review has a panel of fresh sub-agents read the diff and hand Pyor two things: file groups (the changes sorted into labelled folders, important first) and inline hints (short pointers to risks worth a look). No API key, no in-app model run.

The AI here is deliberately quiet: it points you at what matters and gets out of the way. No summaries, no walls of generated text to wade through, just groups to orient you and the occasional hint on a line worth a second look. You read the actual code.

Commands

  • /pyor:review, the primary command. Authors an AI review by default. A panel of fresh sub-agents produces the file grouping + inline hints from the diff, then hands them to Pyor to render. The reviewers run with no context from the calling session (they see only the code, so the review isn't biased by whoever wrote it) across three lenses: correctness, simplicity, and security. After you read and comment in Pyor, click "Send to Claude" to push your comments straight back into the session that opened it.

    Takes an optional grouping intent:

    /pyor:review                      # importance: signal vs noise, important first (default)
    /pyor:review walkthrough          # order the groups as a reading path through the change
    /pyor:review custom "by feature"  # your own grouping instruction
    /pyor:review plain                # skip the AI panel, just open the diff (alias: fast)

Both open your working changes as a local pre-PR review, ready to read before a PR exists; re-running reopens the same review (idempotent).

Install

Claude Code, install the plugin:

/plugin marketplace add Pyor-review/pyor-cli
/plugin install pyor@pyor

Any other agent (Codex, Cursor, Amp, Gemini CLI, Windsurf, Zed, …), install the skill with skills, which mirrors it into your agent's format:

npx skills add https://github.com/Pyor-review/pyor-cli/tree/main/plugins/pyor/skills/pyor-review

Either way, then run /pyor:review (or invoke the pyor-review skill) from any repository. Both drive the same pyor-review flow.

Requirements

  • The Pyor desktop app. It registers the pyor:// URL scheme, renders the review, and exports the review context the AI panel writes against. Grab it at pyor.review; /pyor:review hands you the install command if it's missing.
  • git and node on your PATH.
  • gh (the GitHub CLI) is optional, used only when a command needs GitHub data.

The pyor-review CLI

Both the Claude plugin and the cross-agent skill drive one small, agent-neutral CLI that does the deterministic parts: git resolution, the working-tree revision token (which must match what the app computes so aids cache-hit), the pyor:// deep link, and the ~/.pyor feedback channel. The agent only supplies the analysis (grouping + hints).

Run it without installing:

npx -y pyor-review prepare
npx -y pyor-review --selftest
# or install it: npm install -g pyor-review
# no-install fallback before it's on npm:
#   npx -y --package github:Pyor-review/pyor-cli pyor-review prepare

Subcommands: prepare (resolve repo/head/base + a deterministic session id + revision + the exported review context), open (fire the deep link with the aids), wait (park for "Send to Claude" feedback). pyor-local-review is the plain, no-AI open.

Development

The scripts are self-contained and repo-agnostic, sharing plugins/pyor/scripts/lib.mjs:

node plugins/pyor/scripts/pyor-local-review.mjs --print     # print the deep link, do not open
node plugins/pyor/scripts/pyor-ai-review.mjs prepare        # resolve repo/head/base + revision + context
node plugins/pyor/scripts/pyor-ai-review.mjs --selftest     # run the built-in assertions (incl. session-id determinism)