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

@jagit/hook-copilot

v0.0.1

Published

Reports per-invocation GitHub Copilot CLI usage to JaGit.

Readme

@jagit/hook-copilot

Reports per-invocation GitHub Copilot CLI usage to JaGit.

Setup

The Copilot CLI has no hook mechanism and no persistent session telemetry, so install a shell function that wraps the real copilot binary and reports after each invocation ends:

copilot() {
  command copilot "$@"
  local status=$?
  npx -y @jagit/hook-copilot >/dev/null 2>&1 || true
  return $status
}

Add that function to your shell rc (~/.zshrc, ~/.bashrc, etc.) — it must appear before any alias/PATH entry that would otherwise shadow it. (Users on the legacy gh copilot preview wrapper can apply the same pattern to a gh function instead.) Uninstall by removing the shell function.

For a permanent binary instead of npx -y: npm i -g @jagit/hook-copilot, then call jagit-hook-copilot in the wrapper.

Environment

export JAGIT_BASE_URL="https://your-jagit-host"
export JAGIT_API_KEY="<your DASHBOARD_API_TOKEN>"

Identity defaults to git config user.email; override with JAGIT_GIT_USERNAME.

Notes

  • Copilot CLI exposes no local token/usage telemetry (billing is seat-based), so each report uses a synthetic session id (copilot-<timestamp>-<pid>), zero token counts, and model: "copilot" unless a future CLI version surfaces real usage data.
  • costUsd is always null and will remain so — there is no per-invocation cost to report under seat-based billing.