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

@wispbit/cli

v2.0.29

Published

<p align="center"> <a href="https://wispbit.com"> <picture> <img src="assets/banner.png" alt="wispbit logo" width="100"> </picture> </a> </p>

Readme


Why wispbit?

wispbit is a model-agnostic AI code review tool that runs anywhere and uses your rules.

wispbit works best if you struggle to keep codebase standards alive and transferring tribal knowledge feels repetitive and time consuming.

Installation

  1. npx @wispbit/cli@latest configure
  2. npx @wispbit/cli@latest review

Use cases

See this doc (Github Actions, CI, MCP, Claude Code, Background agents)

Rules

Find examples of free and high quality rules on the wispbit rules page or create your own.

FAQ

Why not use a code editor (Cursor, Claude, Cline, etc) to review code?

  • You could totally do that, however...
  • The tools and prompts for writing and reviewing code are different. We've tried fitting this into existing tools but we found that a specialized tool improves accuracy and reduces noise significantly.
  • When everyone uses a different tool to write code, you need one central place that defines your code standards and enforces them.

How is this different from Bugbot, CodeRabbit, Greptile?

  • 100% open source and runs anywhere.
  • It's specific as opposed to general. Works as expected from day one vs having to fine tune the tool over time with feedback.
  • You have full control of what gets reviewed and what doesn't.
  • You own the data and the prompts.
  • Opinionated and simple. No summaries. No poems. Just violations with actionable feedback. The goal is to get out of your way.

Community

Join the discord community!