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

feedback-central

v0.1.0

Published

CLI to read Feedback Central (admin). No baked-in base URL — pass --base or FC_BASE_URL.

Downloads

19

Readme

feedback-central CLI

Node.js CLI for reading Feedback Central (admin). Zero runtime dependencies.

There is no baked-in base URL. Point it at any deployment:

npx feedback-central --base https://feedback.example.com --help

# persist origin (then --base is optional)
npx feedback-central config set-base https://feedback.example.com

# non-interactive (agents)
FC_BASE_URL=https://feedback.example.com FC_API_KEY=fc_... \
  npx feedback-central feedback list --q "animateClip"

FC_BASE_URL=https://feedback.example.com FC_API_KEY=fc_... \
  npx feedback-central feedback get <id>

FC_BASE_URL=https://feedback.example.com FC_API_KEY=fc_... \
  npx feedback-central feedback context <id>

Also installed as fc when the package is installed globally or locally.

Base URL resolution

  1. --base <url>
  2. FC_BASE_URL
  3. ~/.config/feedback-central/config.json (written by login and config set-base)

Missing all three → exit 1 with instructions. logout does not clear the saved origin.

Auth resolution

  1. FC_API_KEY
  2. ~/.config/feedback-central/api-key (mode 0600)
  3. session cookies from feedback-central login (session.json, mode 0600)

Unauthorized → exit 2.

In this repo

bun run fc still injects https://feedback-central.rockiestar.com when FC_BASE_URL is unset, so existing operator muscle memory works. The published npm package does not do that.

bun run fc -- --help
# after build:
node packages/cli/dist/cli.js --help

Publish

cd packages/cli && npm publish