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

git-fuzzy

v0.0.11

Published

Makes Git a little fuzzier.

Downloads

21

Readme

git-fuzzy

Makes Git a little fuzzier.

by Josh Dick

Install It

npm install -g git-fuzzy

Use It

Installing git-fuzzy should have made it available on your $PATH.

git-fuzzy is a wrapper for Git at the command line. Use Git just like you normally would, except prefix your Git arguments with "fuzzy".

If the last argument looks like a filename, git-fuzzy will attempt to fuzzy match it to the name of a file that has been modified in the working directory of your Git repository. Otherwise, git-fuzzy will just pass your Git arguments through to Git, unmodified.

For example:

> git status
# On branch master
# Changes not staged for commit:
#   (use "git add <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#
#	modified:   another/very/long/path/myawesomefile.ext
#	modified:   some/really/long/path/anotherfile.ext
#
no changes added to commit (use "git add" and/or "git commit -a")

> git fuzzy add awesome

> git status
# On branch master
# Changes to be committed:
#   (use "git reset HEAD <file>..." to unstage)
#
#	modified:   another/very/long/path/myawesomefile.ext
#
# Changes not staged for commit:
#   (use "git add <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#
# modified:   some/really/long/path/anotherfile.ext
#

Typical uses of git-fuzzy include things like:

> git fuzzy add somefile

> git fuzzy reset HEAD somefile

> git fuzzy checkout somefile

To Do

  • Attempt to fuzzy-match against tree-ishes in addition to filenames.
  • Attempt to fuzzy-match against all files in the repository, instead of just those that were modified in the working directory.
  • Attempt to fuzzy-match exact paths, since git-fuzzy treats these as ambiguous.
  • Attempt to fuzzy-match against multiple arguments, or at least arguments other than the last one.

Disclaimer

I take no responsibility if git-fuzzy does unexpected or destructive things to your computer or Git repository. Use it at your own risk. It Works For Me™.

License

git-fuzzy is copyright (c) Joshua Dick, and is licensed under the MIT license. git-fuzzy depends on fuzzy, which is released under the same license.