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

commentcop

v0.2.0

Published

Put your code comments on trial. Powered by Jev.

Readme

commentcop

A little CLI that judges your code comments with Jev.

Is the comment accurate? Does it explain something useful? Or is it just "multiply by two" above value * 2?

Commentcop reads your JS/TS comments with the code around them and scores accuracy and usefulness out of 100. The weakest comments show up first. It respects .gitignore and skips generated code and dependencies.

Give it a go

Grab an API key from TypeSafe, then:

bun x commentcop setup
bun x commentcop

setup saves your key so you only have to do it once. You can also use TYPESAFE_API_KEY. Everything works with npx too.

Point it at another repo, or see every rating:

bun x commentcop ~/code/your-project
bun x commentcop --all

Use --dry-run to preview what it finds without calling Jev. Add exclusions with --ignore or a .commentcopignore file. --help has the rest.

What to expect

We checked 159 comments for about $0.008. The CLI shows progress as ratings come back and gives you an estimated cost at the end.

Some comments need context beyond the nearby code. Check the confidence alongside the score, and use the ratings as a starting point for review.

Comments and surrounding code are sent to TypeSafe for rating. Your setup key stays in ~/.config/commentcop/config.json unless you've set XDG_CONFIG_HOME.

Requires Bun, Node 22.18+ on the 22.x line, or Node 24.11+.

Working on it locally

bun install
bun run dev . --all