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

review-ready

v0.1.0

Published

Pre-PR checklist that catches the small things before your reviewer does: debug statements, missing tests, secrets, TODO debt, and complexity spikes.

Readme

Review Ready

Pre-PR checklist that catches the small things before your reviewer does.

Review Ready scans your git changes and flags issues before you open a pull request — no CI needed, no setup required.

Status bar showing Review Ready: 2 errors

What it checks

| Check | What it catches | |-------|----------------| | Debug statements | console.log, debugger, print(), puts, fmt.Print, println!, var_dump, dd() | | TODO/FIXME debt | TODO, FIXME, HACK, XXX, TEMP, WTF, BUG in newly added lines | | Secrets | AWS keys, GitHub PATs, OpenAI keys, Slack tokens, hardcoded passwords/API keys | | Large files | Files over 500KB accidentally staged | | Missing tests | Source files changed without a corresponding test file | | Complexity | Functions with high cyclomatic complexity (configurable threshold) |

How to use

GitHub Action (CI/CD)

Add to .github/workflows/review-ready.yml:

name: Review Ready
on:
  pull_request:
    branches: [main, master]
jobs:
  review-ready:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0
      - uses: yurukusa/[email protected]

Results appear as inline PR annotations — errors block merge (by default), warnings are informational.

VS Code Extension

  1. Install from the VS Code Marketplace or Open VSX Registry
  2. Make your changes and stage them with git
  3. Click the icon in the Source Control toolbar
  4. Or run Review Ready: Check Changes from the Command Palette (Ctrl+Shift+P)

Results appear in the Review Ready panel in the Activity Bar. The extension also runs automatically whenever you stage or unstage files.

Configuration

All checks can be individually enabled/disabled in Settings → Review Ready.

| Setting | Default | Description | |---------|---------|-------------| | reviewReady.checks.noDebugStatements | true | Flag debug artifacts | | reviewReady.checks.noTodoInChanges | true | Flag TODO/FIXME in new code | | reviewReady.checks.noSecrets | true | Detect potential secrets | | reviewReady.checks.testCoverage | true | Warn when test file is missing | | reviewReady.checks.complexity | true | Flag high-complexity additions | | reviewReady.checks.noLargeFiles | true | Flag files over 500KB | | reviewReady.complexity.threshold | 10 | Cyclomatic complexity threshold |

Supported languages

  • JavaScript / TypeScript (.js, .jsx, .ts, .tsx)
  • Python (.py)
  • Ruby (.rb)
  • Go (.go)
  • Java (.java)
  • Rust (debug statement check only)
  • PHP (debug statement check only)

Why "Review Ready"?

Because the most embarrassing PR review comments are the avoidable ones:

  • "Did you mean to leave this console.log?"
  • "This looks like a hardcoded API key"
  • "There's no test for this file"

Review Ready catches those before they reach your reviewer.

License

MIT