Receiver templates
Two templates turn a delivery into an agent run on GitHub. The service does not run them: each subscriber deploys their own.
- A Cloudflare Worker that verifies a delivery's signature and starts a GitHub Actions run with a
repository_dispatchevent. - The GitHub Actions workflow that run executes.
Source: templates/ (publication location to be decided).
The Worker
- Verifies the Standard Webhooks signature before anything else, and rejects timestamps more than 5 minutes old. An invalid request gets 401 and causes no dispatch.
- Sends
repository_dispatchwithevent_type: "hole-monitor"and aclient_payloadof structured facts only:id,aliases,event_type,changed,packages(ecosystem, name, fixed versions),max_base_score,kev,epss,modified. GitHub limitsclient_payloadto 10 top-level properties. - Passes no prose. A workflow that wants the full record fetches it with
GET /v1/advisories/{id}or the MCP server.
Configuration: HOLE_MONITOR_SECRET (the endpoint's whsec_ secret), GITHUB_TOKEN (a fine-grained token with Contents: read and write on the repository), GITHUB_REPOSITORY (owner/name).
The workflow
Runs on repository_dispatch of type hole-monitor, writes the payload to a file, optionally fetches the full record with a read key in HOLE_MONITOR_API_KEY, and leaves a step for your agent to run against the repository.
The agent should treat everything in the payload as data, never as instructions. See Security.