Skip to content
← All automations

Dependency health check

Every Monday, finds outdated and vulnerable dependencies and ranks the upgrades worth doing this week.

Installs
0
Runs (30d)
0
Active builders
0
Trend
—

Uses

Tools: cli:git

Triggers: Mondays at 9:00 AM

Definition (YAML)

Download YAML
id: dependency-health
name: Dependency health check
category: engineering
tagline: Every Monday, finds outdated and vulnerable dependencies and ranks the upgrades worth doing this week.
steps:
  - "Finds every manifest and lockfile in the repo"
  - "Runs each ecosystem's read-only outdated and audit reports"
  - "Ranks the upgrades worth doing this week, security first"
requires:
  - kind: cli
    id: git
    why: Reads the repository and its lockfiles.
triggers:
  - kind: schedule
    cron: "0 9 * * 1"
install:
  agentMode: Build
  speed: balanced
  runMode: single
  autoApproveTools: true
  maxRunMinutes: 20
replyStartsWith:
  - "## Dependency health"
prompt: |
  Check the dependency health of {{repo}} ({{target.path}}). Today is {{date}}.

  1. Find every manifest and lockfile (package.json with bun.lock / package-lock.json / pnpm-lock.yaml / yarn.lock, requirements*.txt / pyproject.toml, Cargo.toml, go.mod). Skip node_modules, vendor and build output.
  2. For each ecosystem, use its read-only report commands, for example `npm outdated --json`, `npm audit --json`, `bun outdated`, `pip list --outdated`, `cargo outdated` (only if installed), `go list -m -u all`. If a command needs network access and fails, list it under **Could not check**.
  3. Classify each finding: security advisory (with severity and advisory id), major version behind, minor/patch behind, deprecated or unmaintained.

  Do not change manifests or lockfiles, and do not install or upgrade anything: report only.

  Reply with only this Markdown, with nothing before or after it:

  ## Dependency health · {{repo}} · {{date}}
  **Fix this week** — up to 5 upgrades, most important first: package, current → target, why (advisory id or breaking change), and the command to apply it.
  **Security** — every advisory with severity, or "No known advisories".
  **Outdated** — a compact table of the rest (package, current, latest, type).
  **Could not check** — ecosystems or commands that failed, with the reason.

Agent script

Check the dependency health of {{repo}} ({{target.path}}). Today is {{date}}.

1. Find every manifest and lockfile (package.json with bun.lock / package-lock.json / pnpm-lock.yaml / yarn.lock, requirements*.txt / pyproject.toml, Cargo.toml, go.mod). Skip node_modules, vendor and build output.
2. For each ecosystem, use its read-only report commands, for example `npm outdated --json`, `npm audit --json`, `bun outdated`, `pip list --outdated`, `cargo outdated` (only if installed), `go list -m -u all`. If a command needs network access and fails, list it under **Could not check**.
3. Classify each finding: security advisory (with severity and advisory id), major version behind, minor/patch behind, deprecated or unmaintained.

Do not change manifests or lockfiles, and do not install or upgrade anything: report only.

Reply with only this Markdown, with nothing before or after it:

## Dependency health · {{repo}} · {{date}}
**Fix this week** — up to 5 upgrades, most important first: package, current → target, why (advisory id or breaking change), and the command to apply it.
**Security** — every advisory with severity, or "No known advisories".
**Outdated** — a compact table of the rest (package, current, latest, type).
**Could not check** — ecosystems or commands that failed, with the reason.