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-fairy

v0.1.4

Published

Git Fairy turns git history into a whimsical narrative.

Downloads

8

Readme

🧚 Git Fairy

CI npm license

Source control tells you what happened.
Git Fairy tells you the story.

Git Fairy transforms your git log into a whimsical diary of your code's journey.


🚀 Install (once published)

npm install -g git-fairy

🧪 Local Dev / Try It Now (before publishing)

From the project root:

# install dev deps
npm install

# link globally so you can run `git fairy` anywhere
npm link

# OR install globally from the folder (alternative)
npm install -g .

Then in any git repo with commits:

git fairy

Because the binary name is git-fairy, Git lets you also run it as a subcommand (git fairy).

If your repo has no commits yet, you’ll get a friendly notice instead of an error.


🛠 Usage

cd your-project
git fairy            # prints a narrated commit history

Options

--limit <n>       Limit number of commits (integer > 0)
--markdown        Output markdown section per commit
--style <name>    Story style: fairy (default), compact, markdown, json
--json            Shortcut for --style json (machine readable)
--no-color        Reserved for future color disabling
--version         Show version
--since <date>    Filter commits since date
--until <date>    Filter commits until date
--author <pat>    Filter commits by author match

✨ Example Output

🧚 2025-08-12 – 😁 Excited about new features
Added a shiny new authentication system.

🧚 2025-08-13 – 😬 Nervous about breaking things
Quick fix for that thing I broke yesterday.

🧚 2025-08-15 – 🏆 Victory!
Merged feature branch into main. All tests passed. Champagne time.

🎨 Custom Moods

Project Defaults via Config

Create a .git-fairy.json (or .git-fairy.js exporting an object) or add gitFairy key in package.json:

{
	"defaults": {
		"style": "compact",
		"limit": 40,
		"since": "2025-01-01"
	}
}

CLI flags always override config.

Edit src/moods.json to add new keyword → emoji + feeling mappings. The first matching key (substring) wins; default is the fallback.


🤝 Contributing

We welcome pull requests for:

  • New moods / emojis (moods.json)
  • Alternative storytelling styles
  • Language translations
  • VS Code extension integration

See CONTRIBUTING.md for guidelines.


🧩 Project Structure

bin/git-fairy.js   # CLI entry
src/fairy.js       # Orchestration
src/parser.js      # Git log parsing
src/storyteller.js # Narrative building
src/moods.json     # Mood mappings
test/basic.test.js # Smoke test

🧪 Tests

npm test

📦 Publishing Checklist

  • [ ] Pick initial semver (already set to 0.1.0 for first public release)
  • [ ] Fill in author in package.json
  • [ ] Confirm repository, bugs, homepage URLs are correct
  • [ ] Add any badges (npm version, CI) once published
  • [ ] npm login
  • [ ] Run npm test
  • [ ] npm publish --access public

⚖ License

MIT – see LICENSE.


Have an idea? Open an issue and let the Fairy sprinkle some magic.