The servant-github-webhook package

[ Tags: library, mit, web ] [ Propose Tags ]

This package provides servant combinators that make writing safe GitHub webhooks very simple.

It features automatic verification of the digital signatures provided by GitHub in the webhook HTTP requests as well as route dispatching based on repository event type.


[Skip to Readme]

Properties

Versions 0.1.0.0, 0.2.0.0, 0.2.0.1, 0.3.0.0, 0.3.0.1, 0.3.0.2, 0.3.1.0, 0.3.2.0, 0.3.2.1, 0.4.0.0
Change log ChangeLog.md
Dependencies aeson (>=0.11), base (==4.*), base16-bytestring (>=0.1), bytestring (>=0.10), cryptonite (>=0.23), github (>=0.15), github-webhooks (>=0.9), http-types (>=0.9), memory (>=0.14), servant (>=0.11), servant-server (>=0.11), string-conversions (>=0.4), text (>=1.2), unordered-containers (>=0.2), wai (>=3.2) [details]
License MIT
Copyright Jacob Thomas Errington (c) 2016-2018
Author Jacob Thomas Errington
Maintainer servant-github-webhook@mail.jerrington.me
Category Web
Home page https://github.com/tsani/servant-github-webhook
Bug tracker https://github.com/tsani/servant-github-webhook/issues
Source repo head: git clone https://github.com/tsani/servant-github-webhook.git
Uploaded Sat Feb 3 19:23:37 UTC 2018 by tsani
Distributions Stackage:0.3.2.1
Downloads 1369 total (87 in the last 30 days)
Rating (no votes yet) [estimated by rule of succession]
Your Rating
  • λ
  • λ
  • λ
Status Docs not available [build log]
All reported builds failed as of 2018-02-03 [all 3 reports]
Hackage Matrix CI

Modules

  • Servant
    • GitHub
      • Servant.GitHub.Webhook

Downloads

Maintainer's Corner

For package maintainers and hackage trustees


Readme for servant-github-webhook-0.4.0.0

[back to package description]

servant-github-webhook

Build Status Hackage

This library facilitates writing Servant routes that can safely act as GitHub webhooks.

Features:

  • Dispatching to routes based on the type of repository event.
  • Automatic verification of request signatures.
  • Route protection expressed in the type system, so webhook routes and regular routes cannot be confused.

Why use servant-github-webhook?

A webhook server needs to be publicly hosted. How can legitimate requests sent by GitHub be distinguished from (malicious) requests sent by other clients?

When a webhook is configured on a repository, a secret key is added. This key is used by GitHub to compute a signature of the request body that it sends; this signature is included in the request headers. The routing combinators in servant-github-webhook compute the signature of the received request body using the same key, and check that the signature in the request headers matches. If it does, then the request is legitimate.