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

vercel-react-best-practices-report

v3.1.0

Published

Audit React-family files with Vercel React Best Practices and merge results into a JSON report.

Readme

vercel-react-best-practices-report

A CLI/TUI tool powered by provider adapters to audit React and Next.js codebases against the $vercel-react-best-practices skill.

Installation

npm install -g vercel-react-best-practices-report

Or run directly with npx.

Prerequisites

Codex adapter

  • A working Codex CLI environment on the machine.
  • Valid Codex/OpenAI authentication for the current shell session.
  • The $vercel-react-best-practices skill installed in the Codex-compatible skill location.

Claude adapter

  • Claude Code CLI installed and authenticated in the current shell session.
  • The $vercel-react-best-practices skill installed at ~/.claude/skills/vercel-react-best-practices/SKILL.md.

Usage

vercel-react-best-practices-report --adapter <codex|claude> --model <model-id> [--directory <path>] [--concurrency <n>] [provider options]

By default the tool runs with a single worker. Increase concurrency only when you explicitly pass --concurrency.

Options

| Option | Description | | --- | --- | | --adapter, -a | Required. Provider adapter: codex or claude | | --model, -m | Required. Model id for the selected adapter | | --directory, --dir, -d | Optional. Relative path under the current working directory to audit. Defaults to . | | --concurrency, -c | Optional. Number of parallel workers. Default is 1 | | --reasoning-effort, -r | Codex only. Passed through to Codex model_reasoning_effort. Defaults to high | | --effort, -e | Claude only. Passed through to Claude Agent SDK effort. Defaults to high |

Examples

vercel-react-best-practices-report --adapter codex --model gpt-5.4
vercel-react-best-practices-report --adapter codex --model gpt-5.4 --directory packages/web
vercel-react-best-practices-report --adapter codex --model gpt-5.3-codex --reasoning-effort xhigh
vercel-react-best-practices-report --adapter claude --model claude-sonnet-4-6
vercel-react-best-practices-report --adapter claude --model claude-opus-4-1 --effort max --concurrency 2

Output

Results are saved to react-best-practices-report/reports.json inside the audited directory. With the default --directory ., that means the current working directory.

The tool keeps the audit output contract fixed across providers: each file audit must resolve to a JSON object with a single findings array, and the host process validates and merges those results into the final report.

Visualize Results

Drag and drop reports.json into the viewer:

Vercel Best Practices Report Viewer