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 🙏

© 2025 – Pkg Stats / Ryan Hefner

gitnotice

v0.5.1

Published

GITNOTICE - distributed notifications in your VCS

Downloads

13

Readme

Gitnotice - add messaging to your version control

Leave important announcements for your developers when they need them.

Notices are left in commits, and alerts a developer when changes are first pulled in.

nick@local ~/project $ git commit -m 'breaking changes #notice update secrets to include REDIS_PASSWORD'

[master 0e30d2c] breaking changes #notice update secrets to include REDIS_PASSWORD
 1 file changed, 1 insertion(+)

nick@local ~/project $ git push origin master

Writing objects: 100% (3/3), 327 bytes | 327.00 KiB/s, done.
Total 3 (delta 2), reused 0 (delta 0)
To my-test-repo.git
   2de8884..0e30d2c  master -> master
ben@local ~/project $ git pull origin master

remote: Counting objects: 3, done.
remote: Compressing objects: 100% (3/3), done.
remote: Total 3 (delta 2), reused 0 (delta 0)
Unpacking objects: 100% (3/3), done.
From my-test-repo 
 * branch            master     -> FETCH_HEAD
   0e30d2c..702244d  master     -> origin/master
Updating 0e30d2c..702244d
Fast-forward
 gitnotice-test.txt | 1 +
 1 file changed, 1 insertion(+)
 
*********************
::   GIT NOTICES   ::
*********************

0e30d2c Nick Palenchar: update secrets to include REDIS_PASSWORD

(END)
 

Ben can rest easy knowing exactly what to update since last pulling this breaking change 👍

Setup

$ npm i -g gitnotice

gitnotice's hook operates on local git repos, so each one needs to be setup manually. The gitnotice CLI (installed via npm) automates most of this.

In a repo you wish to add gitnotice

~/myproject $ gitnotice init
> gitnotice initialized (0.2.1)

You can also automaticaly add gitnotice to every repo found under a given directory.

~ $ gitnotice init-all
Initialized Gitnotice in the following repositories:
✅ /home/me/myproject
✅ /home/me/myotherproject
✅ /home/me/yetanotherproject

Bugs?

Feel free to submit an issue.

Contributing

Checkout our CONTRIBUTING doc!