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

gh-listener

v0.0.2

Published

A NodeJS listener (receiver) for GitHub events webhooks written in TypeScript

Readme

Github Webhooks Listener

This is a client library for listening (receiving) to GitHub Webhooks and execute a callback on them.

Note: This client library based on the excellent Node Github Hook library.

To Install:

npm install gh-listener

To Use:


import GHClient from "gh-listener";

const github = new GHClient({
  /* options: see below */
});

github.onPush((data) => {
  console.log(data.commits.map(x => x.author)); // prints the authors of the commits
});

Methods and events

The library has the following methods and supports their respective events:

Method | Event | GitHub Reference --- | --- | --- github.onCommitComment(cb) | commit_comment | Reference github.onCreate(cb) | create | Reference github.onDelete(cb) | delete | Reference github.onDeployment(cb) | deployment | Reference github.onDeploymentStatus(cb) | deployment_status | Reference github.onFork(cb) | fork | Reference github.onGollum(cb) | gollum | Reference github.onInstallation(cb) | installation | Reference github.onInstallationRepository(cb) | installation_repository | Reference github.onIssueComment(cb) | issue_comment | Reference github.onIssue(cb) | issue | Reference github.onLabel(cb) | label | Reference github.onMembership(cb) | membership | Reference github.onMilestone(cb) | milestone | Reference github.onOrganization(cb) | organization | Reference github.onOrganizationBlock(cb) | organizationBlock | Reference github.onPageBuild(cb) | page_build | Reference github.onPullRequest(cb) | pull_request | Reference github.onPullRequestReview(cb) | pull_request_review | Reference github.onPullRequestReviewComment(cb) | pull_request_review_comment | Reference github.onPush(cb) | push | Reference github.onRelease(cb) | release | Reference github.onRepository(cb) | repository | Reference github.onStatus(cb) | status | Reference github.onWatch(cb) | watch | Reference

Options

Available options are:

  • host: the host to listen on, defaults to '0.0.0.0'
  • port: the port to listen on, defaults to 3420
  • path: the path for the GitHub callback, defaults to '/github/callback'
  • wildcard: if true, the path for the GitHub callback will be considered valid as long as it starts with the configured path
  • secret: if specified, you must use the same secret in your webhook configuration in GitHub. if a secret is specified, but one is not configured in GitHub, the hook will fail. if a secret is not specified, but one is configured in GitHub, the signature will not be validated and will be assumed to be correct. consider yourself warned. this option can also be a function that takes the following parameters: (request, data, callback). callback is error first and should be passed (err, secret)
  • logger: an optional instance of a logger that supports the "log" and "error" methods and one parameter for data (like console), default is console.
  • https: Options to pass to nodejs https server. If specified, you must follow documentation about nodejs https library (See options in https://nodejs.org/api/https.html#https_https_createserver_options_requestlistener)
  • trustProxy: By default the x-forwarded-for header is trusted when determining the remoteAddress to log for a request. Set this to false to disable this behavior
  • enableHealthcheck: Respond to GET requests with a 204 response for healthcheck purposes
  • healthcheckCode: Override the 204 status code for healthchecks (for systems that aren't friendly with HTTP spec compliance and want a 200, for example)
new GHClient({
	enableHealthcheck: false,
	healthcheckCode: 200,
	host: '0.0.0.0',
	https: {
		ciphers: 'something'
	},
	path: 'listen',
	port: 3000,
	secret: 'mysecretkey',
	trustProxy: true,
	wildcard: true
});

License

MIT