Thirty-Three Security Alerts to Zero
A real operations run on the public agent-swarm repo: 33 open Dependabot alerts became one human-approved grouped pull request. Zero remain open.
- Support
- Triage
- Integrations
- Approvals
Real session, redacted. This ran in our own swarm on 28 September 2026 against the public agent-swarm repository. Names, task identifiers, and internal hosts are removed; the verifiable artifact is the public pull request linked below. All times are Barcelona time.
Request
A standing security workflow on the public desplega-ai/agent-swarm repository: drain the Dependabot alert queue. Triage every open alert, propose a fix for each, and execute only what a human approves. On 28 September the scheduled 08:00 run started with 33 open alerts.
Starting context
The repository's docs site lockfile had accumulated 33 open Dependabot alerts, and there were no open Dependabot pull requests. The workflow is built on the GitHub integration and an approval gate: the first phase is read-only and produces a plan, nothing executes before a human approves that plan, and even then nothing merges itself.
Task breakdown
- 08:00 — run starts. A triage worker reads the alerts. Read-only: no branch, no install, no dismissal.
- 08:03 — plan proposed. All 33 alerts sit in the docs site lockfile. The worker proposes fixing all 33 as one grouped pull request — esbuild, dompurify, js-yaml, fast-uri, postcss, mermaid, and three more, each to its patched version inside its current major — with zero dismissals and zero items needing manual triage. Every item sits on the plan card, pre-selected, waiting for a human.
- 10:12 — human approves the plan. An execution worker starts.
- 10:16 — pull request open. Frozen install, build, and typecheck pass; the docs deploy preview is green. The worker reports one honest failure: alert #132 has no patched version published, so it stays open — expected to close after merge, because the pinned override is outside its vulnerable range. One dependency is held back because its newer minor broke postinstall.
- 10:31 — a human maintainer merges.
Worker roles and handoffs
The triage worker investigates and proposes; it changes nothing. The human holds the gate between proposal and execution — the plan waited two hours for review, and nothing timed out or proceeded without it. The execution worker applies exactly the approved plan and reports what it could not do. The handoff between the two workers is the approved plan card, not a chat transcript.
Approval points
Two gates, both human. First, the plan: nothing executes before approval, and each item can be overridden individually — approve all, approve some, dismiss, or hold. Second, the merge: the swarm opens the pull request but never merges it. The merge at 10:31 was a human maintainer's click.
Output
One grouped pull request: chore(deps): bump vulnerable docs-site dependencies, covering 32 of the 33 alerts — esbuild 0.28.2, dompurify 3.4.13, js-yaml 4.3.2, fast-uri 3.1.6, postcss 8.5.23, mermaid 11.17.2, and three more — with every bump, every pinned override, and the one alert left open listed with its reason in the PR body.
Measurable result
33 open Dependabot alerts before the run; one grouped pull request; zero open Dependabot alerts on the repository when checked on 5 October. The one alert without a patched version closed as predicted once the override landed. Total human time: one plan review and one merge.
What stayed human-owned
Approving the plan, overriding any item in it, the merge, and every dismissal decision. The swarm read, proposed, executed, and verified; the humans decided what was allowed to happen at all.
Sources and tools
- GitHub Dependabot alerts API — the full alert list with severity and patched-version data, read through the
ghCLI. - A plan card with per-item approval — each alert pre-selected with its proposed fix, for a human to approve or override. The pattern is documented in the human-in-the-loop gates playbook.
- Frozen install, build, and typecheck — the verification pass every dependency change must survive, plus the docs deploy preview.
More real sessions: the engineering pull request merged in four hours, the daily research brief that runs every morning, the two-day orchestration loop that carried one request to four human-merged pull requests, and the fully public x402 payment session. Browse everything on the examples index.