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 🙏

© 2024 – Pkg Stats / Ryan Hefner

pullitzer

v1.0.1

Published

Minimal automatic pulls from GitHub

Downloads

3

Readme

Pullitzer

Dead-simple GitHub repo updates.

Usage

$ npm install -g pullitzer
$ pullitzer --example-config
$ vim example.config.json
$ pullitzer --config example.config.json

Then add the URL to your GitHub project's webhooks page.

How it works

Pullitzer runs as a webhook server for GitHub. Whenever it receives a ping, it will fetch (or clone) any remotes attached to that repo. It can also optionally pull those updates into the work tree and run a command whenever it does this. Useful for automatically updating services on GitHub updates!

Everything is configurable in the config.json, which you can see in the source, or generate by using the --example-config command.

Security & webhook secrets

Make sure to set your webhook secret to something random. The webhook secret is used to authenticate requests as genuinely coming from GitHub. If that secret is guessable, someone could flood your pullitzer instance with fake requests and DoS the machine it's on.