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

github-streak

v0.2.1

Published

github-streak is a tool to monitor a GitHub repository and collect short-term information about contributions, triggering a webhook based on the event.

Downloads

7

Readme

github-streak

The purpose of github-streak is to monitor a GitHub repository and collect short-term information about contributions, triggering a webhook based on the event.

Use case

Example: you have a pretty active team and you want to gamify the workflow by displaying "Double kill!" message in a connected Slack channel, when somebody makes a double commit, or "RA-A-AMPAGE" on 6 sequential commits.

What is done now

Currently it works only by posting a formatted message about each commit to a given Slack webhook URL as well as multi commits (2x-5x from 'double' to 'RA-A-AMPAGE').

More integrations and event types will come soon.

How to use

NOTE: Usually it's good to have this running on a free Heroku server, or a local Raspberry Pi.

  1. Define an environmental variable SLACK_WEBHOOK_URL with an address of your Slack Webhook.
  2. Run npm start on a remote always working machine (e.g. Heroku app)
  3. Add a webhook to your GitHub repository to post push events to .../webhooks/push endpoint.
  4. Flexible configuration is comming, but for now to change event message templates you need to fork a repo and update config.json.

Configuration

Templates are defined in config.json file in events in a following way:

"EVENT_TYPE": "TEMPLATE"

Available message replacements in templates:

  1. %an - author name
  2. %au - author username
  3. %ae - author email
  4. %cm - commit message

Example (see config.json):

{
    "multi_timeout": 120000,
    "events": {
        "COMMIT": "%an made a commit: %cm",
        "DOUBLE_COMMIT": "%an got a double commit!",
        "TRIPLE_COMMIT": "%an got a triple commit!"
    }
}

To-do

  • think about other use cases :)
  • monitor BitBucket or other git repository
  • monitor private repositories
  • add more event types and replacers:
"FIRST_COMMIT": "%an opened a coding day by pushing his first commit at %cd: %cm",
  • moar ...

Contributions

...are always welcome.

Tests can be found in /tests folder and be run by npm test or npm run test:watch to continuously run tests on a file change.

Credits

Igor Kuzmenko