Popularity
7.6
Growing
Activity
0.7
Growing
15
3
11
Monthly Downloads: 41
Programming language: Haskell
License: MIT License
Latest version: v0.4.2.0
servant-github-webhook alternatives and similar packages
Based on the "servant" category
-
servant-elm
Automatically derive Elm functions to query servant webservices. -
servant-swagger
Generate Swagger specification for your servant API. -
servant-purescript
Generate PureScript accessor functions for you servant API -
servant-generic
Specify Servant APIs with records. -
servant-snap
A family of combinators for defining webservices APIs and serving them -
servant-auth-cookie
Authentication via encrypted cookies -
servant-router
Servant router for non-server applications. -
servant-js
Automatically derive javascript functions to query servant webservices. -
servant-aeson-specs
generic tests for aeson serialization in servant -
servant-pandoc
Use Pandoc to render servant API documentation -
servant-auth-token-acid
Acid-state backend for servant-auth-token server -
servant-matrix-param
Matrix parameter combinator for servant -
servant-cli
Command line interface for Servant API clients -
servant-cassava
Servant CSV content-type for cassava -
servant-github
Bindings to GitHub API using servant. -
servant-pagination
Type-safe pagination for Servant APIs -
servant-exceptions
Extensible exceptions for servant APIs -
servant-py
Automatically derive python functions to query servant webservices. -
servant-auth-token-leveldb
Leveldb backend for servant-auth-token server -
servant-mock
Derive a mock server for free from your servant API types -
servant-ede
Combinators for rendering EDE templates in servant web applications -
servant-flatten
Utilities for flattening servant API types -
servant-zeppelin-client
Client library for servant-zeppelin combinators. -
servant-zeppelin
Types and definitions of servant-zeppelin combinators. -
servant-reason
Derive Reason types to interact with a Haskell backend -
servant-ruby
Generate a Ruby client from a Servant API with Net -
servant-http2-client
Generate HTTP2 clients from Servant API descriptions. -
servant-match
Standalone implementation of servant’s dispatching mechanism -
servant-kotlin
Automatically derive Kotlin class to query servant webservices -
servant-csharp
Generate servant client library for C# -
servant-options
Provide responses to OPTIONS requests for Servant applications. -
servant-haxl-client
automatical derivation of querying functions for servant webservices -
servant-wasm
Servant support for delivering WebAssembly -
servant-proto-lens
Servant Content-Type for proto-lens protobuf modules. -
servant-generate
Utilities for generating mock server implementations -
servant-jsonrpc-client
Generate JSON-RPC servant clients -
servant-multipart
multipart/form-data (e.g file upload) support for servant
Scout APM: Application Performance Monitoring
Scout gets developers back to coding faster. An intuitive UI streamlines real-time performance insight so you can quickly pinpoint & resolve issues before the customer ever sees them. Start your free trial today!
Promoted
scoutapm.com
Do you think we are missing an alternative of servant-github-webhook or a related project?
README
servant-github-webhook
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.