Weekly dependency audit
Scans every service’s lockfile for known vulnerabilities and opens upgrade pull requests for the safe ones.
Source: scripts/dev/review-runbooks/dependency-audit.yaml. CI checks it with runbook spec validate; teams,
people, skills and called runbooks it names resolve against your server
when you publish it.
apiVersion: therunbook.app/v1kind: Runbookmetadata: id: dependency-audit title: Weekly dependency audit description: Scans every service's lockfile for known vulnerabilities and opens upgrade pull requests for the safe ones. owners: [team:oncall] tags: [security, dependencies, agentic]spec: defaults: { actor: agent } steps: - id: scan title: Scan lockfiles for advisories check: true instructions: Run the advisory scanner over every service repository and list findings by severity. outputs: critical: { type: integer, required: true } high: { type: integer, required: true } - id: upgrades title: Open upgrade pull requests instructions: For each patch-level fix with passing tests, open one pull request per repository. outputs: pull_requests: { type: integer, required: true } - id: triage title: Triage what could not be upgraded automatically actor: human assignee: team:oncall instructions: Decide an owner and a date for every remaining critical or high finding.Publish it to a project:
runbook push dependency-audit.yaml --project <project> --draftrunbook publish dependency-audit --project <project>