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

tender-discussions

v0.2.0

Published

A wrapper around ENTP's Tender, providing a campfire report of pending discussions, and more.

Readme

Unreplied Tender Discussions

Gives you a list of discussions of your Tender support site that nobody has replied to yet.

Installation

npm install --save tender-discussions

or

  • Clone or fork this repo
  • Run npm install .

Execution

You can supply all credentials over the command line:

./bin/tender_discussions --tenderapikey YOUR_TENDER_API_KEY --tendersitename YOUR_TENDER_SITENAME --state pending --campfireaccount YOUR_CAMPFIRE_ACCOUNT --campfirekey YOUR_CAMPFIRE_KEY --campfireroom YOUR_CAMPFIRE_ROOM_ID

... or you can supply them through environment variables. Just copy env.default.sh into an env.sh file, fill out all the credentials there and then run:

source env.sh && ./bin/tender_discussions --state pending

Cli arguments take precedence over the env variables if you provide both.

TODO

  • [] Write some tests