Security

Send GitHub Dependabot alerts to on-call with CallHeim.

Dependabot vulnerability alerts via the repo webhook. CallHeim maps the payload, attaches repeats to the incident that is already open, and pages whoever is on call for the service it belongs to.

dependabotGitHubsource names also accepted: github-dependabot, github-security, dependabot-alert

Setting it up

Create an Integration in CallHeim and choose GitHub Dependabot from the Catalog. You get an ingest URL for that integration, which you paste into GitHub Dependabot’s webhook configuration. CallHeim’s ingest URL takes a JSON request body. The snippet beside this is the shape it expects, with {{WEBHOOK_URL}} replaced by your real URL.

GitHub signs each delivery with the secret you set on its webhook and sends the signature in the X-Hub-Signature-256 header, which CallHeim accepts as well as X-CallHeim-Signature. If you generate a signing secret on this integration, CallHeim requires a valid HMAC-SHA256 signature on every request to it. Without a signing secret, the integration URL is the credential: keep it secret.

CallHeim includes a payload mapping for GitHub Dependabot’s webhook format.

GitHub Dependabot documentation →

Setup snippetdependabot
# GitHub repo/org → Settings → Webhooks → Add webhook
# Payload URL: {{WEBHOOK_URL}}   Content type: application/json
# Events: select "Dependabot alerts".
Check GitHub Dependabot’s current documentation for the exact fields.

After it arrives

What CallHeim does with GitHub Dependabot alerts.

A repeat of the same finding attaches to the incident already open for it, and an Orchestration Rule can route findings by severity, title or any payload field to the team that owns them.

CallHeim maps GitHub Dependabot’s severity or priority field to a P1 to P5 level where the source sends one, and shows a separate, explainable severity suggestion that a person can apply. How severity is suggested →

Each alert source is bound to a service, and the service’s escalation policy (or its team’s) sets who is paged. Alerting and escalation →

If GitHub Dependabot sends a recovery notification, CallHeim records it against the incident.

The thresholds it passes through

Repeat, sender-supplied dedup key
attaches, any age
Repeat, title or subject only
attaches, incident under 24 h old
Flap threshold
4 transitions / 600s
Title correlation
similarity ≥ 0.6, same source and service
Group window default
600s

All defaults are published. You can turn title correlation off or change its threshold, and set the window on your own noise rules; the dedup rule and the flap settings are fixed. A P1 or P2 repeat on an open P3 to P5 incident opens a new incident and pages. How alerts are processed →

CallHeim

Point GitHub Dependabot at CallHeim and see what it does with your alerts.

Start on the free trial, connect GitHub Dependabot and send a test alert to see the incident it opens.