Cuiar
Sign inDownload

Sort the security alerts in your repositories

Open Dependabot alerts across your repos, grouped by package, with the fix version and any open fix PR.

  • On a schedule: Every Monday at 9:30
Use in CuiarRun from your AI agent

What it does

The task

Open the Dependabot alerts in these GitHub repositories: repos. Group the open alerts by package and advisory. For each group, give the severity, the affected repositories, the fixed version, and whether it is a direct or a development dependency. Check whether a pull request with the fix is already open. Send me a table, critical and high first, with links. Do not dismiss alerts or merge pull requests.

  • It works in GitHub, in the workspace you pick, and signs in with passwords from your Cuiar vault.
  • As a routine it runs every Monday at 9:30 (cron 30 9 * * 1).

What you give it

BlankWhat to giveExample
reposThe repositories to check, separated by commasbrightleaf/web, brightleaf/api, brightleaf/admin, brightleaf/docs

What you get back

An example run with the example values above. Your run uses your own data.

23 open alerts in 4 repositories, 9 advisories

PackageSeverityReposFixed inTypeFix PR
nextCriticalweb14.2.25DirectNone
cross-spawnHighweb, admin, docs7.0.5DevelopmentOpen in web only
jsonwebtokenMediumapi9.0.0Directapi#233, CI fails
postcssMediumweb, docs8.4.31DevelopmentNone

... 5 more, all low

1 critical and 1 high advisory have no fix PR for all repos.

Run it in Cuiar

  1. 01

    Open it

    Click Use in Cuiar on this page. The side panel opens with the task in the composer.

  2. 02

    Fill in the blank

    Type repos. Tab moves to the next blank.

  3. 03

    Run it, then repeat it

    Run sends it once. To run it every Monday at 9:30, make a routine on cuiar.com/routines or with the CLI below.

As a routine, from the terminal

cuiar routines create "Sort the security alerts in your repositories" --schedule "30 9 * * 1" --time-zone Europe/Berlin \
  "Open the Dependabot alerts in these GitHub repositories: brightleaf/web, brightleaf/api, brightleaf/admin, brightleaf/docs. Group the open alerts by package and advisory. For each group, give the severity, the affected repositories, the fixed version, and whether it is a direct or a development dependency. Check whether a pull request with the fix is already open. Send me a table, critical and high first, with links. Do not dismiss alerts or merge pull requests."

Run it from your AI agent

Claude Code, Codex, Cursor and other MCP clients reach Cuiar at https://mcp.cuiar.com/mcp. Add the server one time, then ask for the task in plain words, or call create_routine yourself.

1. Add Cuiar to Claude Code

claude mcp add --transport http cuiar https://mcp.cuiar.com/mcp

2. Ask your agent

Use the Cuiar tool create_routine to run my "Sort the security alerts in your repositories" template with repos = brightleaf/web, brightleaf/api, brightleaf/admin, brightleaf/docs.

Setup for other agents: AI agents.

The tool call

{
  "name": "create_routine",
  "arguments": {
    "name": "Sort the security alerts in your repositories",
    "task": "Open the Dependabot alerts in these GitHub repositories: brightleaf/web, brightleaf/api, brightleaf/admin, brightleaf/docs. Group the open alerts by package and advisory. For each group, give the severity, the affected repositories, the fixed version, and whether it is a direct or a development dependency. Check whether a pull request with the fix is already open. Send me a table, critical and high first, with links. Do not dismiss alerts or merge pull requests.",
    "schedule": "30 9 * * 1",
    "time_zone": "Europe/Berlin"
  }
}

Related templates

All engineering templates

  • Engineering

    List pull requests that wait for review

    Open PRs across your repos with age, reviewers and CI status, the oldest first.

    On a schedule: Every weekday at 10:00
    • GitHub

  • EngineeringAsks first

    Write release notes from merged pull requests

    Merged PRs since the last release, grouped and written for users, saved as a draft GitHub release.

    You start it: When you start it
    • GitHub

  • Engineering

    Read the changelogs before you upgrade dependencies

    Breaking changes, security fixes and upgrade steps for each outdated package, from its release notes.

    You start it: When you start it
    • GitHub
    • npm
    • PyPI

  • EngineeringAsks first

    Label and sort new GitHub issues

    Labels, a priority and a possible duplicate for each new issue, applied after you approve them.

    On an event: When a new issue is opened
    • GitHub

  • Engineering

    Find flaky tests in your CI runs

    Tests that fail and then pass on the same commit, with the count and the error, from your recent runs.

    You start it: When you start it
    • GitHub
    • Google Sheets

  • Engineering

    Find why a deploy failed

    The error from the build log, the change that caused it and a suggested fix, sent when a deploy fails.

    On an event: When a deploy fails in Vercel
    • Vercel
    • GitHub