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

@gilangjavier/prfa

v0.1.0

Published

PR Follow-up Assistant CLI for tracking open/stale pull requests and drafting follow-up messages.

Readme

PR Follow-up Assistant (prfa)

A small cross-platform Node.js CLI to scan your open GitHub PRs, highlight stale ones, and generate follow-up message templates.

Features

  • Scan open PRs authored by a GitHub user
  • Detect stale PRs by inactivity threshold (--days)
  • Output markdown summary for easy posting into issues/chats/notes
  • Generate follow-up templates for stale PRs

Requirements

  • Node.js 18+
  • GitHub CLI (gh) installed and authenticated (gh auth status)

Install

Global install:

npm i -g @gilangjavier/prfa

Or run without installing:

npx @gilangjavier/prfa scan --user gilangjavier --days 7

Usage

prfa scan --user gilangjavier --days 7

(If you used npx, replace prfa with npx @gilangjavier/prfa.)

Or via npm script (for contributors):

npm run scan -- --user gilangjavier --days 7

Example Output

# PR Follow-up Summary for @gilangjavier

Generated: 2026-03-17T03:43:00.000Z
Stale threshold: 7 days

## Open PRs (2)
- [owner/repo#12](https://github.com/owner/repo/pull/12) — feat: improve parser _(inactive 2d)_

## Stale PRs (1)
- [owner/repo#11](https://github.com/owner/repo/pull/11) — fix: flaky tests _(inactive 10d)_

## Suggested follow-up templates
### owner/repo#11
Hi maintainers, friendly follow-up on this PR 👋

- Is there anything I should adjust to move this forward?
- Happy to update tests/docs if needed.

Thanks for your time!

Development

npm test

Release readiness

Dry-run package publish:

npm publish --dry-run

Publishing to npm is not done automatically. You need npm login and publish rights.

License

MIT