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

patreon-webhook-signature

v1.2.4

Published

Simple way to verify webhook requests from Patreon using your webhook secret

Downloads

54

Readme

patreon-webhook-signature

Simple way to verify webhook requests from Patreon using your webhook secret.

Install

npm i patreon-webhook-signature

Example (Express)

Explanation: For the hashes to match the body of the request must be exactly how Patreon intended it after being sent to your endpoint. Even converting it to JSON will change enough data for it to mismatch the hash. This means that the body of the request must be as raw and untouched as possible resulting in the expected hash. You may have to fiddle around with your codebase in order to get this to work properly, so use the below example as a form of guideance.

const express = require('express');
const bodyParser = require('body-parser');
const pws = require('patreon-webhook-signature');

const app = express();

// *REQUIRED*
// req.body MUST be raw for the patreon webhook endpoint
// otherwise <PWS>.verify always returns false.
// The body must be raw as it must be exactly how Patreon
// sent the original webhook request, otherwise if even
// a single byte is different the hash will be vastly different.
// *However*, this turns req.body into a buffer - see comment below.
app.use('/api/v1/patreon', bodyParser.raw({ type: 'application/json' })); // This must also be above defining routes or parsing with json etc.
app.use(bodyParser.json());

app.post('/api/v1/patreon', async (req, res) => {
    const verified = pws.verify(
        process.env.PATREON_SECRET, 
        req.headers['x-patreon-signature'],
        req.body
    );
    
    if (!verified || req.headers['x-patreon-signature'] == null) {
        return res.status(401).send('Invalid Authentication.');
    }

    // As req.body is now a Buffer, you must use this
    // if you require the body parameters as if it
    // was a normal JSON request.
    const body = pws.body(req.body);

    console.log(`(Patreon) ${body.included[0].attributes.full_name} just pledged.`);
});