handling-webhooks — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited handling-webhooks (Agent Skill) and scored it 92/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 2 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 2 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
A webhook is an untrusted HTTP request from an external system announcing an event. Treat the endpoint as a public, hostile-input surface.
body with the shared secret) before trusting anything. Reject unsigned/invalid requests. Compare signatures in constant time.
over exact bytes; re-serialized JSON won't match.
queue (see designing-a-job-queue). Providers retry on slow/failed responses, so blocking work in the handler causes timeouts and duplicate deliveries.
event id and make handling idempotent; don't assume events arrive in order.
validate shape, and never feed it unsanitized into a query/command/path.
accept (bad signature/payload); 5xx = transient, please retry. Don't 200 a request you failed to actually process.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.