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

@willh/mgit

v2.0.4

Published

Run the same git command in every Git repository under the current directory

Readme

mgit

Run the same git command in every Git repository under the current directory.

This package ships the official mgit binaries for macOS, Linux and Windows, so npx works without any build step and without running install scripts.

$ mgit
================================================================================
📂 Folder: repo-a │ Branch: main
================================================================================
 M src/main.rs

================================================================================
📂 Folder: repo-b │ Branch: feature/login
================================================================================
(clean, no output)

================================================================================

Install

npm install --global @willh/mgit     # or: pnpm add -g @willh/mgit, yarn global add @willh/mgit
npx @willh/mgit                      # run without installing
bunx @willh/mgit

Other ways to install (Homebrew-free one line installers, release archives, cargo install) are documented in the main README.

Usage

mgit                       # git status -s in every repository
mgit pull                  # git pull in every repository
mgit fetch --all --prune
mgit log --oneline -n 3
mgit -q status             # quiet: no per repository headers
mgit --depth 2 fetch       # search two directory levels deep
mgit --list                # only list the repositories that were found
mgit --fail-fast pull      # stop at the first repository that fails

--help lists every option, --version prints the version. Anything that is not an mgit option is handed to git verbatim, so mgit -c core.pager=cat status works too.

See the main README for the full documentation (including the exit codes and the environment variables) and for the 正體中文說明.

How this package works

  • The tarball contains the release binaries for six targets: aarch64-apple-darwin, x86_64-apple-darwin, aarch64-unknown-linux-musl, x86_64-unknown-linux-musl (static, runs on every Linux distribution), aarch64-pc-windows-msvc and x86_64-pc-windows-msvc.
  • bin/mgit.js spawns the binary for your platform with inherited stdio, so colours, pagers, Ctrl+C and interactive git prompts behave exactly like a native run.
  • There is no postinstall script: installing the package never executes code and works with --ignore-scripts, pnpm, yarn and bun.
  • Every release is published from GitHub Actions with provenance, so you can verify where the binaries came from with npm audit signatures.

MGIT_BINARY=/path/to/mgit overrides the bundled binary, which is useful when you build mgit yourself.

Requirements

  • Node.js 20 or newer
  • git on PATH (mgit is a wrapper around your own git installation)

License

MIT