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

pk-sweeper

v0.1.10

Published

Conservative GitHub issue and pull request sweep recommendations.

Downloads

78

Readme

pk-sweeper

pk-sweeper is a conservative GitHub issue and pull request maintenance helper. It reviews open items, writes markdown recommendation reports, and can later sync review comments or apply high-confidence decisions only when explicitly requested.

The normal local workflow is safe by default:

cd path/to/target-repo
pksweeper sweep

sweep auto-detects the GitHub repository from the current checkout's origin remote, checks both issues and pull requests with balanced selection, and writes reports without closing, commenting, or merging.

Install

Requires Node.js 24 or newer, the GitHub CLI (gh), and the Codex CLI.

npm install -g pk-sweeper

Or run without installing globally:

npx pk-sweeper sweep

Commands

pksweeper sweep
pksweeper plan
pksweeper quick
pksweeper apply-decisions

sweep is recommended for coding sessions. It runs a preflight before review work starts and prints:

  • resolved GitHub repository
  • current working directory
  • target checkout directory
  • output workspace
  • Codex CLI path
  • target checkout clean/dirty status

If a required check fails, it stops before doing review work.

Target Repository Resolution

PK Sweeper resolves the target repository in this order:

  1. --repo <owner>/<repo>
  2. PKSWEEPER_TARGET_REPO
  3. GH_REPO
  4. the current checkout's GitHub origin remote
  5. sweeper.config.json targetRepo

For local use, prefer running from the target repo checkout and leave targetRepo as null. Placeholder values such as owner/repo are ignored and reported.

Example config:

{
  "targetRepo": null,
  "docsUrl": null,
  "pluginEcosystem": null,
  "extraStopWords": [],
  "protectedLabels": ["security", "beta-blocker", "release-blocker", "maintainer"]
}

Output

By default, reports are written to a sibling workspace:

../<target-repo>.pksweeper/

Typical files:

  • quick-plan.json
  • items/<number>.md
  • quick-summary.md
  • todo.md
  • plan.md
  • artifacts/reviews/...

Safety

  • Review and sweep runs are proposal-only.
  • apply-decisions is the command that can mutate GitHub.
  • Maintainer-authored items are not auto-closed.
  • Protected labels block automated close actions.
  • Reviews fail if Codex modifies the target checkout.
  • Dirty target checkouts stop preflight unless --allow-dirty is passed.
  • Placeholder target repos are ignored instead of queried.

Use --allow-dirty only when local target checkout changes are intentional:

pksweeper sweep --allow-dirty

Examples

Preview candidates:

pksweeper plan

Run a small safe sweep:

pksweeper sweep --agents 2 --concurrency 1 --batch-size 1 --max-pages 2

Run against an explicit repository:

pksweeper sweep --repo octocat/Hello-World

Apply already-reviewed decisions later, after inspection:

pksweeper apply-decisions --limit 5

Do not pass --merge-prs unless you intentionally want high-confidence PR merge proposals to be merged.

Development

npm install
npm run build
npm run check
npm pack

The published package includes only:

  • dist
  • prompts
  • schema
  • README.md
  • LICENSE

Generated review archives, local workspaces, and target-repo artifacts are not included in the npm package.