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

@reneturcios/reviewthread

v0.1.0

Published

Classify pull-request review comments as actionable, noise, closed, stale, or duplicate from caller-supplied facts: author kind, thread state, failing-check linkage, and body. Returns one verdict per comment with the exact rule that fired as evidence.

Readme

reviewthread

A pull-request review thread collects everything: a maintainer pointing at a genuinely broken check, a bot cheering "LGTM", the same coverage note posted twice, a comment on code that has since been rewritten. reviewthread sorts a batch of those comments into the five buckets a reviewer actually acts on — actionable, noise, closed, stale, and duplicate — and, for each one, names the exact rule that put it there, so the verdict can be checked rather than trusted.

You supply the facts, per comment: an id, the author's name, whether the author is a bot or a human, the body, the thread state (open, resolved, or outdated), and optionally whether the comment is attached to a currently failing check and the id of another comment it duplicates. Nothing is fetched; the classification is a pure function of what you pass in.

The rules run in a fixed order and the first match wins. A resolved thread is closed and an outdated one is stale, whatever else is true of the comment. A comment whose duplicate_of is non-empty after trimming is a duplicate, and its evidence names the trimmed target id. A comment attached to a failing check is actionable — that outranks everything a bot might say. Only then does authorship matter: a bot whose body is praise-only (after trimming, lowercasing, collapsing whitespace, and stripping trailing ! and . characters, the body is exactly one of a pinned eleven-phrase set such as lgtm, looks good to me, or ship it) is noise, and any other bot comment with no failing check is noise too. What remains — an open human comment — is actionable.

Two judgement calls are pinned. A duplicate_of that is absent, empty, or whitespace-only counts as no duplicate at all. And praise is judged against the exact phrase set only: a bot saying "great job, but the tests fail" is a generic bot comment, not praise-only, because the whole normalized body must match a phrase.

Malformed input — a missing or empty comments array, a comment that is not an object, a missing, empty, or non-string id or author, an author_kind outside bot / human, a missing or non-string body, a state outside open / resolved / outdated, a non-boolean failing_check, or a non-string duplicate_of — is a validation error naming the offending path, with no partial result. Unknown extra fields are ignored, including inside comment items.

CLI

npx @reneturcios/reviewthread triage --input args.json
npx @reneturcios/reviewthread --version

args.json contains the full arguments object:

{
  "comments": [
    {
      "id": "c1",
      "author": "ci-bot",
      "author_kind": "bot",
      "body": "Coverage dropped below the threshold.",
      "state": "open",
      "failing_check": true
    },
    {
      "id": "c2",
      "author": "dependabot[bot]",
      "author_kind": "bot",
      "body": "LGTM!",
      "state": "open"
    },
    {
      "id": "c3",
      "author": "marisol",
      "author_kind": "human",
      "body": "This still races when the cache is cold.",
      "state": "open"
    }
  ]
}

The result is printed as JSON:

{
  "comments": [
    {
      "id": "c1",
      "author": "ci-bot",
      "verdict": "actionable",
      "evidence": "comment is attached to a failing check"
    },
    {
      "id": "c2",
      "author": "dependabot[bot]",
      "verdict": "noise",
      "evidence": "praise-only bot comment with no failing check"
    },
    {
      "id": "c3",
      "author": "marisol",
      "verdict": "actionable",
      "evidence": "open human comment"
    }
  ],
  "counts": {
    "actionable": 2,
    "noise": 1,
    "closed": 0,
    "stale": 0,
    "duplicate": 0
  },
  "total": 3
}

Exit codes: 0 on success, 1 on a runtime error (including an unreadable or invalid input file, or invalid input), 2 on a usage error.

MCP server

npx -y @reneturcios/reviewthread mcp

MCP client config:

{
  "mcpServers": {
    "reviewthread": {
      "command": "npx",
      "args": ["-y", "@reneturcios/reviewthread", "mcp"]
    }
  }
}

Tools

  • triage_review_comments — Classify pull-request review comments as actionable, noise, closed, stale, or duplicate from caller-supplied comment facts.

    • comments (array, required, at least 1 item) — the review comments to classify. Each item:
      • id (string, required, non-empty) — comment identifier
      • author (string, required, non-empty) — comment author name
      • author_kind (string, required, bot or human) — whether the author is a bot or a human
      • body (string, required, may be empty) — comment body text
      • state (string, required, open, resolved, or outdated) — thread state of the comment
      • failing_check (boolean, optional, absent means false) — whether the comment is attached to a currently failing check
      • duplicate_of (string, optional) — id of another comment this one duplicates

    Returns {comments, counts, total}, where comments is one {id, author, verdict, evidence} per input comment in input order, counts is {actionable, noise, closed, stale, duplicate} in that key order, and total is the number of input comments.

Docker

docker run -i ghcr.io/cloudcorprecords/reviewthread
docker run --rm -v "$PWD:/w" ghcr.io/cloudcorprecords/reviewthread triage --input /w/args.json

Development

npm install
npm run build   # tsc -> dist/
npm test        # tsx --test test/*.test.ts (pure local, no network)
npm run dev     # run the CLI from source

License

MIT — Copyright (c) 2026 Rene Turcios