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

@scruple/comments

v0.3.5

Published

Semantic rules for source-code comments.

Readme

@scruple/comments

Checks for source comments that restate code, contradict visible behavior, preserve disabled code or change history, use unnecessary prose, or lack actionable guidance.

pnpm add --save-dev @scruple/comments

Rules cover comment usefulness, correctness, disabled code, change history, concision, actionable TODOs, justified suppression directives, and actionable deprecations.

Comment source, value, and surrounding context are independently bounded before provider evaluation, with truncation flags included in the evidence. Suppression directives remain auditable when they disable comments/require-justified-suppressions on their own line; their normal effect on other candidates is unchanged. During an engine run, TODO selection uses the configured provider to classify bounded non-directive comments, including todo:, to-do:, FIXME, HACK, and @todo JSDoc tags, without treating ordinary phrases such as “to-do list” as maintenance markers. Selected comments then receive the separate actionability decision.

Follow the published quickstart, browse the rule registry, compare providers, or write a custom rule.