Skip to content

Dependabot security alerts as a hub status category #15

@ooloth

Description

@ooloth

Why

Security vulnerabilities in watched repos need timely attention, but hub surfaces nothing about them today — they're only visible if you check GitHub's security tab directly.

Current state

hub status shows PRs awaiting review and open/assigned GitHub issues. There is no section for security alerts. Dependabot alert data is available via the GitHub REST API but is not fetched or displayed.

Ideal state

  • hub status includes a "security alerts" section listing open Dependabot alerts across configured repos
  • Each alert shows: repo, package name, severity, and URL
  • Alerts are sorted by severity (critical → high → medium → low)
  • The section is omitted when there are no open alerts
  • The workflow is configurable per-repo in hub.toml using a github-dependabot workflow name

Starting points

  • clients/src/github.rs — existing GitHub client pattern to follow
  • config/src/toml.rs — where WorkflowConfig variants are defined
  • workflows/src/status.rs — where new workflow calls should be added

QA plan

  1. Add a github-dependabot workflow entry to hub.toml for a repo with known open Dependabot alerts
  2. Run hub status — expect a "security alerts" section listing each alert with severity and URL
  3. Dismiss an alert in GitHub, re-run hub status — expect that alert no longer appears
  4. Add the workflow for a repo with no open alerts — expect the section is omitted from output
  5. Remove all github-dependabot entries from hub.toml — expect no security alerts section appears

Done when

hub status shows open Dependabot security alerts for configured repos, sorted by severity.

Metadata

Metadata

Assignees

No one assigned

    Labels

    laterBacklog, not yet sequenced

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions