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

gmc

v1.0.1

Published

Local GitWeb dashboard and AI-assisted commit messages for Git repositories

Readme

GMC

A local Git workbench for AI-assisted development. Start with gmc web: a browser dashboard for Git state, repository tasks, changes, commit history, and AI-generated commit messages.

GMC Web dashboard

Install

npm install -g gmc
gmc --version

Start With Web

cd path/to/your/repo
gmc web

gmc web starts a local server for the current repository and opens a visual Git dashboard.

| Web surface | Why it helps | | --- | --- | | Branch, upstream, ahead/behind state | Decide whether to push, pull, or keep working before committing. | | Selectable working tree files | Commit only the files you intend to include. | | Branch tree and commit graph | See where current work sits in repository history. | | Clickable commit details | Inspect the full message and file summary without leaving the page. | | Repository task board | Keep lightweight Markdown tasks in .gmc/tasks with the code. | | Background task status | Track AI commit-message rewrites from the same dashboard. |

Daily Commit Loop

gmc install --all
git add .
git commit -m gmc

When the commit message is exactly gmc, the commit returns immediately. GMC records the new commit, generates a better commit message in the background, and rewrites that commit only if it is still HEAD.

Check background work:

gmc status
gmc retry HEAD

Commands

| Command | Status | Purpose | | --- | --- | --- | | gmc --version | Ready | Print the installed CLI version. | | gmc web [--port 4277] [--no-open] | Ready | Start or open the local GitWeb dashboard. | | gmc install --all [--port 4277] | Ready | Install hooks and create the local Web link. | | gmc install-hooks | Ready | Install commit-message and task-status hooks. | | gmc status | Ready | Show current repository status and recent background work. | | gmc message | Ready | Generate a commit message from staged changes. | | gmc commit [--no-edit] | Ready | Generate a message, commit staged changes, and update related task statuses. | | gmc retry [commit] | Ready | Queue another background message attempt. |

Requirements

  • Git repository
  • Node.js 18 or newer
  • codex CLI for AI commit-message generation
  • Optional: claude CLI when gmc agent claude is configured

Safety

  • GMC Web serves 127.0.0.1 only.
  • Credentials are read from environment variables and are not written to the repository.
  • Repository tasks are ordinary Markdown files under .gmc/tasks.
  • Commit flows can move related tasks forward to doing, review, or done based on the commit diff, but task file changes are left in the working tree for a later user-selected commit.
  • Background commit-message rewrites only target the recorded commit while it is still HEAD.
  • Automatic rewrites are skipped during merge/rebase-style operations and for signed commits.