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

vibereviewing

v0.7.0

Published

Split a GitHub PR into AI-reviewable layers

Readme

vibereview

Split a GitHub PR into three layered commits (A/B/C) so reviewers focus on what needs human judgment.

Install

pnpm add -g vibereviewing

Requires Node 20+, git, and gh CLI (authenticated).

Quick start

vibereview runs against a local checkout of the target repo (the one the PR lives in), not the directory where vibereview itself is installed. cd there first.

Using Claude (Anthropic)

export ANTHROPIC_API_KEY=sk-ant-...
cd path/to/your/repo
vibereview split https://github.com/owner/repo/pull/1234

Default model: claude-haiku-4-5 (cheap, sufficient for diff classification). Override to a stronger model if needed:

vibereview split https://github.com/owner/repo/pull/1234 \
  --provider claude --model claude-opus-4-7

Using OpenAI

export OPENAI_API_KEY=sk-...
cd path/to/your/repo
vibereview split https://github.com/owner/repo/pull/1234

Default model: gpt-5-mini (cheap, sufficient for diff classification). Override to a stronger model if needed:

vibereview split https://github.com/owner/repo/pull/1234 \
  --provider openai --model gpt-5

Provider auto-detection

If both ANTHROPIC_API_KEY and OPENAI_API_KEY are set, Claude wins. Pass --provider openai (or --provider claude) to force a choice.

Dry run (no PR, no push)

Inspect the classification manifest without touching git or GitHub:

vibereview split https://github.com/owner/repo/pull/1234 --dry-run
# or, equivalently:
vibereview manifest https://github.com/owner/repo/pull/1234

Commands

  • vibereview split <pr> — open a layered companion PR.
  • vibereview manifest <pr> — print the classification manifest (no git, no PR).
  • vibereview verify <pr> — re-verify a companion PR (no LLM call).

See vibereview --help for flags.

Configuration

Put a .vibereview.yml at the repo root. The most important section is floors — paths in those globs are forced to a minimum layer regardless of how innocent the hunk looks. Defaults are empty.

See the included example.

Security

⚠️ vibereview sends your PR diff to the configured LLM provider. If your diff contains secrets, those secrets are sent to that provider. vibereview does not scrub secrets in v1.