tai42-webhook-verifier-github 0.1.0__tar.gz

tai42_webhook_verifier_github-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

tai42_webhook_verifier_github-0.1.0/MANIFEST.in

@@ -0,0 +1 @@
+prune tests

tai42_webhook_verifier_github-0.1.0/NOTICE

@@ -0,0 +1,5 @@
+tai42-webhook-verifier-github
+Copyright 2026 tai42
+
+This product includes software developed at tai42 (https://tai42.ai).
+Licensed under the Apache License, Version 2.0.

tai42_webhook_verifier_github-0.1.0/PKG-INFO

@@ -0,0 +1,196 @@
+Metadata-Version: 2.4
+Name: tai42-webhook-verifier-github
+Version: 0.1.0
+Summary: GitHub webhook-signature verifier plugin for the TAI ecosystem: a per-provider WebhookVerifier that checks each delivery's X-Hub-Signature-256 HMAC before the payload is dispatched.
+Author-email: tai42 <oss@tai42.ai>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://tai42.ai
+Project-URL: Repository, https://github.com/tai42ai/tai-webhook-verifier-github
+Project-URL: Issues, https://github.com/tai42ai/tai-webhook-verifier-github/issues
+Project-URL: Changelog, https://github.com/tai42ai/tai-webhook-verifier-github/blob/main/CHANGELOG.md
+Keywords: tai,webhook,verifier,github,hmac,signature,security
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Operating System :: OS Independent
+Classifier: Topic :: Security
+Classifier: Typing :: Typed
+Requires-Python: >=3.13
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: tai42-contract<0.2,>=0.1
+Dynamic: license-file
+
+# tai42-webhook-verifier-github
+
+[![CI](https://github.com/tai42ai/tai-webhook-verifier-github/actions/workflows/ci.yml/badge.svg)](https://github.com/tai42ai/tai-webhook-verifier-github/actions/workflows/ci.yml)
+[![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE)
+
+The GitHub webhook-signature verifier plugin for the TAI ecosystem — a
+per-provider `WebhookVerifier` that authenticates each inbound GitHub delivery
+before the platform parses or dispatches its payload.
+
+> A webhook door can bind a named verifier to a topic; this plugin supplies the
+> `github` verifier.
+
+GitHub signs every webhook delivery with an HMAC-SHA256 over the **exact raw
+request body**, keyed by the shared secret, and sends it in the
+`X-Hub-Signature-256` header as `"sha256=" + hexdigest`. `GitHubWebhookVerifier`
+recomputes that HMAC over the raw bytes and compares it in constant time. It
+returns `None` on success and raises `WebhookVerificationError` on any failure.
+
+Its only tai-\* dependency is `tai42-contract` (the interface it registers
+through); the HMAC work is pure standard library (`hmac` / `hashlib`). It
+**never** imports the skeleton — the plugin is contract-facing.
+
+## The TAI ecosystem
+
+TAI is an open-source runtime for MCP tools, agents, and workflows. A trigger
+fires a tool from an inbound event; a webhook verifier is the door's bouncer —
+the per-provider check that authenticates a delivery before any hook runs. This
+package is the GitHub verifier. The ecosystem is open-ended: any package can
+supply a verifier, so this repo is this verifier's own full doc home, and the
+documentation site covers the platform-level story:
+
+- Triggers & webhooks concept: https://tai42.ai/concepts/triggers-and-webhooks
+- Build a webhook verifier (author guide): https://tai42.ai/guides/authors/webhook-verifier
+- Ecosystem catalog: https://tai42.ai/reference/catalog
+
+## Install
+
+Requires **Python 3.13+**. Nothing is on PyPI yet, so install from source — clone
+this repo alongside your `tai42-skeleton` checkout and add it as an editable
+dependency of the environment that runs the server:
+
+```bash
+git clone https://github.com/tai42ai/tai-webhook-verifier-github
+cd tai-skeleton   # or your own app checkout
+uv add --editable ../tai-webhook-verifier-github   # once published: uv add tai42-webhook-verifier-github
+```
+
+## How it loads — `lifecycle_modules`
+
+The platform loads this plugin through the manifest's **`lifecycle_modules`**
+field. That field is **import-only**: the host simply imports each listed module
+to run its registration side effect. Importing `tai42_webhook_verifier_github`
+calls `tai42_app.webhook_verifiers.register("github", GitHubWebhookVerifier())`,
+binding the `github` verifier on the app handle.
+
+```jsonc
+{
+  // Import-only modules: loaded purely for their registration side effect.
+  // `lifecycle_modules` are imported WITHOUT going through the extension
+  // registry's validation — only `extensions_modules` run that. So this entry
+  // is a plain registration, not an extension.
+  "lifecycle_modules": ["tai42_webhook_verifier_github"]
+}
+```
+
+`lifecycle_modules` entries are imported as-is, with no validation step —
+only `extensions_modules` go through the extension registry's validation. This
+entry is therefore a plain registration, not an extension.
+
+## Configuration — the secret never leaves the environment
+
+A verifier is bound to a topic with `{verifier, config}`. This plugin's `config`
+holds only the **name** of the environment variable that carries the secret —
+never the secret itself:
+
+```json
+{ "verifier": "github", "config": { "secret_env": "GITHUB_WEBHOOK_SECRET" } }
+```
+
+At verify time the secret is read from `os.environ[config["secret_env"]]`. A
+**missing** env var raises loudly (`KeyError`) and an **empty** one raises
+`ValueError` — verification fails **CLOSED**, so a misconfigured secret never
+becomes a silently-unauthenticated door.
+
+> **Secret hygiene.** The secret lives only in an environment variable. Never
+> commit it to a file, a fixture, a manifest, or a URL. The example secret below
+> (`It's a Secret to Everybody`) is GitHub's own published example — it is a
+> placeholder for docs and tests, never a real secret.
+
+## End-to-end
+
+1. **Create the GitHub webhook.** In your repo → *Settings* → *Webhooks* → *Add
+   webhook*, set the *Payload URL* to your platform's public door, e.g.
+   `https://<your-host>/universal_webhook/github-events`, *Content type*
+   `application/json`, and a **Secret**. Store that same secret in the
+   environment as `GITHUB_WEBHOOK_SECRET` on the platform.
+
+2. **List `tai42_webhook_verifier_github` in the manifest** under
+   `lifecycle_modules` (see above) so the `github` verifier is registered at
+   boot.
+
+3. **Bind the verifier to the topic.** Through the skeleton's authenticated
+   route:
+
+   ```bash
+   curl -X PUT https://<your-host>/api/hooks/topics/github-events/verifier \
+     -H "Authorization: Bearer $TAI_API_TOKEN" \
+     -H "Content-Type: application/json" \
+     -d '{"verifier": "github", "config": {"secret_env": "GITHUB_WEBHOOK_SECRET"}}'
+   ```
+
+4. **Register a hook** on the `github-events` topic that runs a demo tool (e.g. a
+   tool that logs the event). Now push to the repo → GitHub signs and POSTs the
+   delivery → the door verifies the `X-Hub-Signature-256` HMAC → the hook fires
+   and the tool runs. A delivery with a missing, malformed, or wrong signature is
+   rejected before any hook runs.
+
+### Simulate a signed delivery locally
+
+Compute the signature over the exact body with the same secret and POST it — this
+is what a genuine GitHub delivery looks like on the wire:
+
+```bash
+# The secret lives only in the environment — never hard-coded here.
+export GITHUB_WEBHOOK_SECRET="It's a Secret to Everybody"   # GitHub's example placeholder
+
+BODY='{"zen":"Keep it logically awesome."}'
+SIG="sha256=$(printf '%s' "$BODY" \
+  | openssl dgst -sha256 -hmac "$GITHUB_WEBHOOK_SECRET" -r \
+  | cut -d ' ' -f1)"
+
+curl -X POST http://127.0.0.1:8000/universal_webhook/github-events \
+  -H "Content-Type: application/json" \
+  -H "X-GitHub-Event: ping" \
+  -H "X-Hub-Signature-256: $SIG" \
+  --data-raw "$BODY"
+```
+
+`printf '%s'` (not `echo`) sends the body with no trailing newline, so the bytes
+signed match the bytes POSTed exactly — the HMAC is over the raw body.
+
+## Verification rules
+
+`verify(body, headers, config)` is an `async` method — the caller awaits it. It
+raises `WebhookVerificationError` when:
+
+- the `X-Hub-Signature-256` header is **missing** (lookup is case-insensitive),
+- the value is not prefixed exactly `sha256=` (e.g. a `sha1=` prefix),
+- the hex after the prefix is not exactly **64** characters (wrong/truncated),
+- the recomputed digest **does not match** (the final compare uses
+  `hmac.compare_digest` — constant-time).
+
+A missing `secret_env` env var raises `KeyError` and an empty one raises
+`ValueError` (fails closed), not `WebhookVerificationError`.
+
+## Development
+
+```bash
+uv sync
+uv run pytest -q
+uv run ruff check .
+uv run ruff format --check .
+uv run pyright
+```
+
+`[tool.uv.sources]` resolves `tai42-contract` from a sibling checkout for local
+development; the published wheel floors it from the index.
+
+## License
+
+Apache-2.0. See `LICENSE` and `NOTICE`.

tai42_webhook_verifier_github-0.1.0/README.md

@@ -0,0 +1,171 @@
+# tai42-webhook-verifier-github
+
+[![CI](https://github.com/tai42ai/tai-webhook-verifier-github/actions/workflows/ci.yml/badge.svg)](https://github.com/tai42ai/tai-webhook-verifier-github/actions/workflows/ci.yml)
+[![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE)
+
+The GitHub webhook-signature verifier plugin for the TAI ecosystem — a
+per-provider `WebhookVerifier` that authenticates each inbound GitHub delivery
+before the platform parses or dispatches its payload.
+
+> A webhook door can bind a named verifier to a topic; this plugin supplies the
+> `github` verifier.
+
+GitHub signs every webhook delivery with an HMAC-SHA256 over the **exact raw
+request body**, keyed by the shared secret, and sends it in the
+`X-Hub-Signature-256` header as `"sha256=" + hexdigest`. `GitHubWebhookVerifier`
+recomputes that HMAC over the raw bytes and compares it in constant time. It
+returns `None` on success and raises `WebhookVerificationError` on any failure.
+
+Its only tai-\* dependency is `tai42-contract` (the interface it registers
+through); the HMAC work is pure standard library (`hmac` / `hashlib`). It
+**never** imports the skeleton — the plugin is contract-facing.
+
+## The TAI ecosystem
+
+TAI is an open-source runtime for MCP tools, agents, and workflows. A trigger
+fires a tool from an inbound event; a webhook verifier is the door's bouncer —
+the per-provider check that authenticates a delivery before any hook runs. This
+package is the GitHub verifier. The ecosystem is open-ended: any package can
+supply a verifier, so this repo is this verifier's own full doc home, and the
+documentation site covers the platform-level story:
+
+- Triggers & webhooks concept: https://tai42.ai/concepts/triggers-and-webhooks
+- Build a webhook verifier (author guide): https://tai42.ai/guides/authors/webhook-verifier
+- Ecosystem catalog: https://tai42.ai/reference/catalog
+
+## Install
+
+Requires **Python 3.13+**. Nothing is on PyPI yet, so install from source — clone
+this repo alongside your `tai42-skeleton` checkout and add it as an editable
+dependency of the environment that runs the server:
+
+```bash
+git clone https://github.com/tai42ai/tai-webhook-verifier-github
+cd tai-skeleton   # or your own app checkout
+uv add --editable ../tai-webhook-verifier-github   # once published: uv add tai42-webhook-verifier-github
+```
+
+## How it loads — `lifecycle_modules`
+
+The platform loads this plugin through the manifest's **`lifecycle_modules`**
+field. That field is **import-only**: the host simply imports each listed module
+to run its registration side effect. Importing `tai42_webhook_verifier_github`
+calls `tai42_app.webhook_verifiers.register("github", GitHubWebhookVerifier())`,
+binding the `github` verifier on the app handle.
+
+```jsonc
+{
+  // Import-only modules: loaded purely for their registration side effect.
+  // `lifecycle_modules` are imported WITHOUT going through the extension
+  // registry's validation — only `extensions_modules` run that. So this entry
+  // is a plain registration, not an extension.
+  "lifecycle_modules": ["tai42_webhook_verifier_github"]
+}
+```
+
+`lifecycle_modules` entries are imported as-is, with no validation step —
+only `extensions_modules` go through the extension registry's validation. This
+entry is therefore a plain registration, not an extension.
+
+## Configuration — the secret never leaves the environment
+
+A verifier is bound to a topic with `{verifier, config}`. This plugin's `config`
+holds only the **name** of the environment variable that carries the secret —
+never the secret itself:
+
+```json
+{ "verifier": "github", "config": { "secret_env": "GITHUB_WEBHOOK_SECRET" } }
+```
+
+At verify time the secret is read from `os.environ[config["secret_env"]]`. A
+**missing** env var raises loudly (`KeyError`) and an **empty** one raises
+`ValueError` — verification fails **CLOSED**, so a misconfigured secret never
+becomes a silently-unauthenticated door.
+
+> **Secret hygiene.** The secret lives only in an environment variable. Never
+> commit it to a file, a fixture, a manifest, or a URL. The example secret below
+> (`It's a Secret to Everybody`) is GitHub's own published example — it is a
+> placeholder for docs and tests, never a real secret.
+
+## End-to-end
+
+1. **Create the GitHub webhook.** In your repo → *Settings* → *Webhooks* → *Add
+   webhook*, set the *Payload URL* to your platform's public door, e.g.
+   `https://<your-host>/universal_webhook/github-events`, *Content type*
+   `application/json`, and a **Secret**. Store that same secret in the
+   environment as `GITHUB_WEBHOOK_SECRET` on the platform.
+
+2. **List `tai42_webhook_verifier_github` in the manifest** under
+   `lifecycle_modules` (see above) so the `github` verifier is registered at
+   boot.
+
+3. **Bind the verifier to the topic.** Through the skeleton's authenticated
+   route:
+
+   ```bash
+   curl -X PUT https://<your-host>/api/hooks/topics/github-events/verifier \
+     -H "Authorization: Bearer $TAI_API_TOKEN" \
+     -H "Content-Type: application/json" \
+     -d '{"verifier": "github", "config": {"secret_env": "GITHUB_WEBHOOK_SECRET"}}'
+   ```
+
+4. **Register a hook** on the `github-events` topic that runs a demo tool (e.g. a
+   tool that logs the event). Now push to the repo → GitHub signs and POSTs the
+   delivery → the door verifies the `X-Hub-Signature-256` HMAC → the hook fires
+   and the tool runs. A delivery with a missing, malformed, or wrong signature is
+   rejected before any hook runs.
+
+### Simulate a signed delivery locally
+
+Compute the signature over the exact body with the same secret and POST it — this
+is what a genuine GitHub delivery looks like on the wire:
+
+```bash
+# The secret lives only in the environment — never hard-coded here.
+export GITHUB_WEBHOOK_SECRET="It's a Secret to Everybody"   # GitHub's example placeholder
+
+BODY='{"zen":"Keep it logically awesome."}'
+SIG="sha256=$(printf '%s' "$BODY" \
+  | openssl dgst -sha256 -hmac "$GITHUB_WEBHOOK_SECRET" -r \
+  | cut -d ' ' -f1)"
+
+curl -X POST http://127.0.0.1:8000/universal_webhook/github-events \
+  -H "Content-Type: application/json" \
+  -H "X-GitHub-Event: ping" \
+  -H "X-Hub-Signature-256: $SIG" \
+  --data-raw "$BODY"
+```
+
+`printf '%s'` (not `echo`) sends the body with no trailing newline, so the bytes
+signed match the bytes POSTed exactly — the HMAC is over the raw body.
+
+## Verification rules
+
+`verify(body, headers, config)` is an `async` method — the caller awaits it. It
+raises `WebhookVerificationError` when:
+
+- the `X-Hub-Signature-256` header is **missing** (lookup is case-insensitive),
+- the value is not prefixed exactly `sha256=` (e.g. a `sha1=` prefix),
+- the hex after the prefix is not exactly **64** characters (wrong/truncated),
+- the recomputed digest **does not match** (the final compare uses
+  `hmac.compare_digest` — constant-time).
+
+A missing `secret_env` env var raises `KeyError` and an empty one raises
+`ValueError` (fails closed), not `WebhookVerificationError`.
+
+## Development
+
+```bash
+uv sync
+uv run pytest -q
+uv run ruff check .
+uv run ruff format --check .
+uv run pyright
+```
+
+`[tool.uv.sources]` resolves `tai42-contract` from a sibling checkout for local
+development; the published wheel floors it from the index.
+
+## License
+
+Apache-2.0. See `LICENSE` and `NOTICE`.

tai42_webhook_verifier_github-0.1.0/pyproject.toml

@@ -0,0 +1,95 @@
+[build-system]
+requires = ["setuptools>=77", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "tai42-webhook-verifier-github"
+version = "0.1.0"
+description = "GitHub webhook-signature verifier plugin for the TAI ecosystem: a per-provider WebhookVerifier that checks each delivery's X-Hub-Signature-256 HMAC before the payload is dispatched."
+readme = "README.md"
+requires-python = ">=3.13"
+license = "Apache-2.0"
+license-files = ["LICENSE", "NOTICE"]
+authors = [
+    { name = "tai42", email = "oss@tai42.ai" },
+]
+keywords = ["tai", "webhook", "verifier", "github", "hmac", "signature", "security"]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Intended Audience :: Developers",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.13",
+    "Operating System :: OS Independent",
+    "Topic :: Security",
+    "Typing :: Typed",
+]
+dependencies = [
+    # The pure interface contract this verifier registers through (the global
+    # tai42_app handle and the WebhookVerifier / WebhookVerificationError types).
+    # The HMAC work is pure standard library (hmac / hashlib) — no other tai-*
+    # dependency is needed.
+    "tai42-contract>=0.1,<0.2",
+]
+
+[project.urls]
+Homepage = "https://tai42.ai"
+Repository = "https://github.com/tai42ai/tai-webhook-verifier-github"
+Issues = "https://github.com/tai42ai/tai-webhook-verifier-github/issues"
+Changelog = "https://github.com/tai42ai/tai-webhook-verifier-github/blob/main/CHANGELOG.md"
+
+[dependency-groups]
+# Public dev/test tooling (installed by default with `uv sync`).
+dev = [
+    "pytest>=8",
+    "pytest-cov>=5",
+    "ruff>=0.6",
+    "pyright>=1.1.389",
+    # The plugin-spec test parses tai-plugin.yml.
+    "pyyaml>=6",
+]
+
+[tool.setuptools]
+package-dir = { "" = "src" }
+
+[tool.setuptools.packages.find]
+where = ["src"]
+include = ["tai42_webhook_verifier_github*"]
+
+[tool.setuptools.package-data]
+tai42_webhook_verifier_github = ["py.typed", "tai-plugin.yml"]
+
+[tool.uv]
+cache-keys = [{ file = "pyproject.toml" }]
+
+
+# The version floors in [project] are the compatibility contract; these path
+# sources resolve the sibling checkouts while the packages are unpublished.
+# They are not part of wheel metadata.
+[tool.uv.sources]
+tai42-contract = { path = "../tai-contract", editable = true }
+[tool.ruff]
+src = ["src"]
+target-version = "py313"
+line-length = 120
+
+[tool.ruff.lint]
+select = ["E", "W", "F", "I", "UP", "B", "C4", "SIM", "PIE", "PT", "RUF", "TID"]
+
+[tool.ruff.lint.flake8-tidy-imports.banned-api]
+"tai42_skeleton".msg = "tai42-webhook-verifier-github is contract-facing: it never imports tai42-skeleton."
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+xfail_strict = true
+filterwarnings = ["error"]
+
+[tool.coverage.run]
+source = ["tai42_webhook_verifier_github"]
+
+[tool.coverage.report]
+fail_under = 95
+
+[tool.pyright]
+include = ["src", "tests"]
+pythonVersion = "3.13"
+typeCheckingMode = "basic"

tai42_webhook_verifier_github-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

tai42_webhook_verifier_github-0.1.0/src/tai42_webhook_verifier_github/__init__.py

@@ -0,0 +1,19 @@
+"""GitHub webhook-signature verifier plugin.
+
+Importing this package registers a :class:`GitHubWebhookVerifier` under the name
+``"github"`` on the app handle's ``webhook_verifiers`` facet, so a webhook door can
+bind ``github`` to a topic. Import-only: loaded via the manifest's
+``lifecycle_modules`` purely for the registration side effect. Depends only on
+``tai42-contract``.
+"""
+
+from __future__ import annotations
+
+from tai42_contract.app import tai42_app
+
+from tai42_webhook_verifier_github.verifier import GitHubWebhookVerifier
+
+# Registration side effect run on import; a duplicate name raises loudly.
+tai42_app.webhook_verifiers.register("github", GitHubWebhookVerifier())
+
+__all__ = ["GitHubWebhookVerifier"]

tai42_webhook_verifier_github-0.1.0/src/tai42_webhook_verifier_github/tai-plugin.yml

@@ -0,0 +1,22 @@
+spec_version: 1
+namespace: tai42
+name: webhook-verifier-github
+package: tai42-webhook-verifier-github
+version: 0.1.0
+description: "GitHub webhook-signature verifier plugin for the TAI ecosystem: a per-provider WebhookVerifier that checks each delivery's X-Hub-Signature-256 HMAC before the payload is dispatched."
+license: Apache-2.0
+homepage: https://tai42.ai
+repository: https://github.com/tai42ai/tai-webhook-verifier-github
+contract: ">=0.1,<0.2"
+categories: [webhooks, security]
+tags: [webhooks, github, hmac, security]
+permissions:
+  network: false
+  subprocess: false
+  filesystem: false
+provides:
+  - kind: webhook-verifier
+    name: github
+    module: tai42_webhook_verifier_github
+    description: "Verify a GitHub webhook delivery's X-Hub-Signature-256 HMAC before dispatch."
+    tags: [github, hmac]

tai42_webhook_verifier_github-0.1.0/src/tai42_webhook_verifier_github/verifier.py

@@ -0,0 +1,87 @@
+"""GitHub webhook-signature verifier.
+
+Authenticates an inbound delivery's ``X-Hub-Signature-256`` HMAC-SHA256 (over the
+exact raw body, keyed by the shared secret). The secret is named by
+``config["secret_env"]`` and read from the environment at verify time; a missing or
+empty secret raises loudly so the door fails CLOSED. Standard-library only
+(``hmac`` / ``hashlib``).
+"""
+
+from __future__ import annotations
+
+import hashlib
+import hmac
+import os
+from collections.abc import Mapping
+from typing import Any
+
+from tai42_contract.webhooks import WebhookVerificationError
+
+# A well-formed value is ``sha256=`` followed by 64 hex chars.
+_SIGNATURE_HEADER = "X-Hub-Signature-256"
+_SIGNATURE_PREFIX = "sha256="
+_HEX_DIGEST_LEN = hashlib.sha256().digest_size * 2  # 64
+
+
+class GitHubWebhookVerifier:
+    """Verifies a GitHub webhook delivery's ``X-Hub-Signature-256`` HMAC.
+
+    Registered under the name ``"github"`` on the app handle's
+    ``webhook_verifiers`` facet. Satisfies the
+    :class:`~tai42_contract.webhooks.WebhookVerifier` protocol.
+    """
+
+    # Signature covers the raw body only, so a door binding this verifier must reject GET.
+    post_only = True
+
+    async def verify(self, body: bytes, headers: Mapping[str, str], config: dict[str, Any]) -> None:
+        """Verify a GitHub webhook, or raise ``WebhookVerificationError``.
+
+        ``body`` is the exact raw request bytes the HMAC is computed over; ``headers``
+        are looked up case-insensitively; ``config`` is
+        ``{"secret_env": "<ENV VAR NAME>"}``. Fails CLOSED: a missing config key,
+        missing env var, or empty secret raises loudly (``KeyError`` / ``ValueError``),
+        never an ordinary signature failure.
+        """
+        # Fail closed: an empty secret would still key the HMAC into a signature anyone could forge.
+        secret_env = config["secret_env"]
+        secret = os.environ[secret_env].encode("utf-8")
+        if not secret:
+            raise ValueError(f"webhook secret environment variable {secret_env!r} is set but empty")
+
+        signature = _header_lookup(headers, _SIGNATURE_HEADER)
+        if signature is None:
+            raise WebhookVerificationError(f"missing {_SIGNATURE_HEADER} header")
+
+        if not signature.startswith(_SIGNATURE_PREFIX):
+            raise WebhookVerificationError(f"{_SIGNATURE_HEADER} is not prefixed {_SIGNATURE_PREFIX!r}")
+
+        provided_hex = signature[len(_SIGNATURE_PREFIX) :]
+        if len(provided_hex) != _HEX_DIGEST_LEN:
+            raise WebhookVerificationError(f"{_SIGNATURE_HEADER} digest is not {_HEX_DIGEST_LEN} hex characters")
+        # Reject a non-hex digest as an ordinary verification failure, not an unhandled parse error.
+        try:
+            provided_digest = bytes.fromhex(provided_hex)
+        except ValueError as exc:
+            raise WebhookVerificationError(f"{_SIGNATURE_HEADER} digest is not valid hex") from exc
+
+        expected_digest = hmac.new(secret, body, hashlib.sha256).digest()
+
+        # Constant-time compare so a mismatch position cannot be timed.
+        if not hmac.compare_digest(provided_digest, expected_digest):
+            raise WebhookVerificationError(f"{_SIGNATURE_HEADER} digest mismatch")
+
+
+def _header_lookup(headers: Mapping[str, str], name: str) -> str | None:
+    """Return ``name``'s value from ``headers`` case-insensitively.
+
+    HTTP header names are case-insensitive and the caller may pass a plain ``dict``.
+    """
+    target = name.lower()
+    for key, value in headers.items():
+        if key.lower() == target:
+            return value
+    return None
+
+
+__all__ = ["GitHubWebhookVerifier"]

tai42_webhook_verifier_github-0.1.0/src/tai42_webhook_verifier_github.egg-info/PKG-INFO

@@ -0,0 +1,196 @@
+Metadata-Version: 2.4
+Name: tai42-webhook-verifier-github
+Version: 0.1.0
+Summary: GitHub webhook-signature verifier plugin for the TAI ecosystem: a per-provider WebhookVerifier that checks each delivery's X-Hub-Signature-256 HMAC before the payload is dispatched.
+Author-email: tai42 <oss@tai42.ai>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://tai42.ai
+Project-URL: Repository, https://github.com/tai42ai/tai-webhook-verifier-github
+Project-URL: Issues, https://github.com/tai42ai/tai-webhook-verifier-github/issues
+Project-URL: Changelog, https://github.com/tai42ai/tai-webhook-verifier-github/blob/main/CHANGELOG.md
+Keywords: tai,webhook,verifier,github,hmac,signature,security
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Operating System :: OS Independent
+Classifier: Topic :: Security
+Classifier: Typing :: Typed
+Requires-Python: >=3.13
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: tai42-contract<0.2,>=0.1
+Dynamic: license-file
+
+# tai42-webhook-verifier-github
+
+[![CI](https://github.com/tai42ai/tai-webhook-verifier-github/actions/workflows/ci.yml/badge.svg)](https://github.com/tai42ai/tai-webhook-verifier-github/actions/workflows/ci.yml)
+[![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE)
+
+The GitHub webhook-signature verifier plugin for the TAI ecosystem — a
+per-provider `WebhookVerifier` that authenticates each inbound GitHub delivery
+before the platform parses or dispatches its payload.
+
+> A webhook door can bind a named verifier to a topic; this plugin supplies the
+> `github` verifier.
+
+GitHub signs every webhook delivery with an HMAC-SHA256 over the **exact raw
+request body**, keyed by the shared secret, and sends it in the
+`X-Hub-Signature-256` header as `"sha256=" + hexdigest`. `GitHubWebhookVerifier`
+recomputes that HMAC over the raw bytes and compares it in constant time. It
+returns `None` on success and raises `WebhookVerificationError` on any failure.
+
+Its only tai-\* dependency is `tai42-contract` (the interface it registers
+through); the HMAC work is pure standard library (`hmac` / `hashlib`). It
+**never** imports the skeleton — the plugin is contract-facing.
+
+## The TAI ecosystem
+
+TAI is an open-source runtime for MCP tools, agents, and workflows. A trigger
+fires a tool from an inbound event; a webhook verifier is the door's bouncer —
+the per-provider check that authenticates a delivery before any hook runs. This
+package is the GitHub verifier. The ecosystem is open-ended: any package can
+supply a verifier, so this repo is this verifier's own full doc home, and the
+documentation site covers the platform-level story:
+
+- Triggers & webhooks concept: https://tai42.ai/concepts/triggers-and-webhooks
+- Build a webhook verifier (author guide): https://tai42.ai/guides/authors/webhook-verifier
+- Ecosystem catalog: https://tai42.ai/reference/catalog
+
+## Install
+
+Requires **Python 3.13+**. Nothing is on PyPI yet, so install from source — clone
+this repo alongside your `tai42-skeleton` checkout and add it as an editable
+dependency of the environment that runs the server:
+
+```bash
+git clone https://github.com/tai42ai/tai-webhook-verifier-github
+cd tai-skeleton   # or your own app checkout
+uv add --editable ../tai-webhook-verifier-github   # once published: uv add tai42-webhook-verifier-github
+```
+
+## How it loads — `lifecycle_modules`
+
+The platform loads this plugin through the manifest's **`lifecycle_modules`**
+field. That field is **import-only**: the host simply imports each listed module
+to run its registration side effect. Importing `tai42_webhook_verifier_github`
+calls `tai42_app.webhook_verifiers.register("github", GitHubWebhookVerifier())`,
+binding the `github` verifier on the app handle.
+
+```jsonc
+{
+  // Import-only modules: loaded purely for their registration side effect.
+  // `lifecycle_modules` are imported WITHOUT going through the extension
+  // registry's validation — only `extensions_modules` run that. So this entry
+  // is a plain registration, not an extension.
+  "lifecycle_modules": ["tai42_webhook_verifier_github"]
+}
+```
+
+`lifecycle_modules` entries are imported as-is, with no validation step —
+only `extensions_modules` go through the extension registry's validation. This
+entry is therefore a plain registration, not an extension.
+
+## Configuration — the secret never leaves the environment
+
+A verifier is bound to a topic with `{verifier, config}`. This plugin's `config`
+holds only the **name** of the environment variable that carries the secret —
+never the secret itself:
+
+```json
+{ "verifier": "github", "config": { "secret_env": "GITHUB_WEBHOOK_SECRET" } }
+```
+
+At verify time the secret is read from `os.environ[config["secret_env"]]`. A
+**missing** env var raises loudly (`KeyError`) and an **empty** one raises
+`ValueError` — verification fails **CLOSED**, so a misconfigured secret never
+becomes a silently-unauthenticated door.
+
+> **Secret hygiene.** The secret lives only in an environment variable. Never
+> commit it to a file, a fixture, a manifest, or a URL. The example secret below
+> (`It's a Secret to Everybody`) is GitHub's own published example — it is a
+> placeholder for docs and tests, never a real secret.
+
+## End-to-end
+
+1. **Create the GitHub webhook.** In your repo → *Settings* → *Webhooks* → *Add
+   webhook*, set the *Payload URL* to your platform's public door, e.g.
+   `https://<your-host>/universal_webhook/github-events`, *Content type*
+   `application/json`, and a **Secret**. Store that same secret in the
+   environment as `GITHUB_WEBHOOK_SECRET` on the platform.
+
+2. **List `tai42_webhook_verifier_github` in the manifest** under
+   `lifecycle_modules` (see above) so the `github` verifier is registered at
+   boot.
+
+3. **Bind the verifier to the topic.** Through the skeleton's authenticated
+   route:
+
+   ```bash
+   curl -X PUT https://<your-host>/api/hooks/topics/github-events/verifier \
+     -H "Authorization: Bearer $TAI_API_TOKEN" \
+     -H "Content-Type: application/json" \
+     -d '{"verifier": "github", "config": {"secret_env": "GITHUB_WEBHOOK_SECRET"}}'
+   ```
+
+4. **Register a hook** on the `github-events` topic that runs a demo tool (e.g. a
+   tool that logs the event). Now push to the repo → GitHub signs and POSTs the
+   delivery → the door verifies the `X-Hub-Signature-256` HMAC → the hook fires
+   and the tool runs. A delivery with a missing, malformed, or wrong signature is
+   rejected before any hook runs.
+
+### Simulate a signed delivery locally
+
+Compute the signature over the exact body with the same secret and POST it — this
+is what a genuine GitHub delivery looks like on the wire:
+
+```bash
+# The secret lives only in the environment — never hard-coded here.
+export GITHUB_WEBHOOK_SECRET="It's a Secret to Everybody"   # GitHub's example placeholder
+
+BODY='{"zen":"Keep it logically awesome."}'
+SIG="sha256=$(printf '%s' "$BODY" \
+  | openssl dgst -sha256 -hmac "$GITHUB_WEBHOOK_SECRET" -r \
+  | cut -d ' ' -f1)"
+
+curl -X POST http://127.0.0.1:8000/universal_webhook/github-events \
+  -H "Content-Type: application/json" \
+  -H "X-GitHub-Event: ping" \
+  -H "X-Hub-Signature-256: $SIG" \
+  --data-raw "$BODY"
+```
+
+`printf '%s'` (not `echo`) sends the body with no trailing newline, so the bytes
+signed match the bytes POSTed exactly — the HMAC is over the raw body.
+
+## Verification rules
+
+`verify(body, headers, config)` is an `async` method — the caller awaits it. It
+raises `WebhookVerificationError` when:
+
+- the `X-Hub-Signature-256` header is **missing** (lookup is case-insensitive),
+- the value is not prefixed exactly `sha256=` (e.g. a `sha1=` prefix),
+- the hex after the prefix is not exactly **64** characters (wrong/truncated),
+- the recomputed digest **does not match** (the final compare uses
+  `hmac.compare_digest` — constant-time).
+
+A missing `secret_env` env var raises `KeyError` and an empty one raises
+`ValueError` (fails closed), not `WebhookVerificationError`.
+
+## Development
+
+```bash
+uv sync
+uv run pytest -q
+uv run ruff check .
+uv run ruff format --check .
+uv run pyright
+```
+
+`[tool.uv.sources]` resolves `tai42-contract` from a sibling checkout for local
+development; the published wheel floors it from the index.
+
+## License
+
+Apache-2.0. See `LICENSE` and `NOTICE`.

tai42_webhook_verifier_github-0.1.0/src/tai42_webhook_verifier_github.egg-info/SOURCES.txt

@@ -0,0 +1,14 @@
+LICENSE
+MANIFEST.in
+NOTICE
+README.md
+pyproject.toml
+src/tai42_webhook_verifier_github/__init__.py
+src/tai42_webhook_verifier_github/py.typed
+src/tai42_webhook_verifier_github/tai-plugin.yml
+src/tai42_webhook_verifier_github/verifier.py
+src/tai42_webhook_verifier_github.egg-info/PKG-INFO
+src/tai42_webhook_verifier_github.egg-info/SOURCES.txt
+src/tai42_webhook_verifier_github.egg-info/dependency_links.txt
+src/tai42_webhook_verifier_github.egg-info/requires.txt
+src/tai42_webhook_verifier_github.egg-info/top_level.txt

tai42_webhook_verifier_github-0.1.0/src/tai42_webhook_verifier_github.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

tai42_webhook_verifier_github-0.1.0/src/tai42_webhook_verifier_github.egg-info/requires.txt

@@ -0,0 +1 @@
+tai42-contract<0.2,>=0.1

tai42_webhook_verifier_github-0.1.0/src/tai42_webhook_verifier_github.egg-info/top_level.txt

@@ -0,0 +1 @@
+tai42_webhook_verifier_github