List and dismiss GitHub Dependabot alerts across a repository and organization via the REST API

domain: docs.github.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Use a token with the security_events or repo scope (or the Dependabot alerts fine-grained permission).
  2. Call GET /repos/{owner}/{repo}/dependabot/alerts to list alerts, filtering by state, severity, ecosystem, or package.
  3. Call GET /repos/{owner}/{repo}/dependabot/alerts/{alert_number} for manifest path and vulnerable version range details.
  4. Call PATCH /repos/{owner}/{repo}/dependabot/alerts/{alert_number} with state=dismissed and a dismissed_reason (e.g. tolerable_risk, inaccurate, not_used) plus an optional comment, or state=open to reopen.
  5. Aggregate results across repositories with the org-level GET /orgs/{org}/dependabot/alerts endpoint for a fleet-wide view.

Known gotchas

Related routes

Retrieve GitHub code scanning and Dependabot alerts via the REST API
docs.github.com · 6 steps · unrated
List, triage, and resolve GitHub secret scanning alerts via the REST API
docs.github.com · 5 steps · unrated
List organization-wide secret scanning alerts via the GitHub REST API
docs.github.com · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans