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

@boring-stack-pkg/eslint-plugin-comment-hygiene

v0.2.0

Published

ESLint rules that catch agent-generated comment patterns: narrative prose ('Here we...', 'Now we...'), PR/issue references, and similar drift-prone metadata that belongs in commit messages, not source.

Readme

eslint-plugin-comment-hygiene

npm source

ESLint rules that catch agent-generated comment patterns:

  • no-narration-comments — flags step-by-step prose like // Here we…, // Now we…, // First, …, // Let's …. Describes the sequence of operations a reader can already see; a tell that the comment was written by an agent narrating its own changes.
  • no-pr-reference-comments — flags PR/issue numbers (#123, PR 42, see #5, closes #99) and GitHub PR/issue URLs. Repo-history references belong in commit messages and PR descriptions — they rot when the repo moves or the numbering changes.

JSDoc-style block comments (/** … */) are exempt from no-narration-comments so descriptions / @param / @returns don't false-positive.

Install

pnpm add -D @boring-stack-pkg/eslint-plugin-comment-hygiene

Peer deps: eslint >= 8.57, @typescript-eslint/parser >= 8, typescript >= 5.

Use (flat config)

import tsParser from "@typescript-eslint/parser";
import commentHygiene from "@boring-stack-pkg/eslint-plugin-comment-hygiene";

export default [
  {
    files: ["**/*.{ts,tsx}"],
    languageOptions: { parser: tsParser },
    plugins: { "comment-hygiene": commentHygiene },
    rules: {
      "comment-hygiene/no-narration-comments": "error",
      "comment-hygiene/no-pr-reference-comments": "error",
    },
  },
];

Or use the bundled config:

import commentHygiene from "@boring-stack-pkg/eslint-plugin-comment-hygiene";

export default [commentHygiene.configs.recommended];

Rules

| Rule | Description | Fixable | | -------------------------------------------------------------------- | ----------------------------------------------------------------------------- | ------- | | no-narration-comments | Disallow narrative comments like "Here we…", "Now we…", "First, …", "Let's …" | – | | no-pr-reference-comments | Disallow PR / issue references (#123, PR 42, GitHub URLs) in comments | – |

License

MIT.