triage-dependabot-alerts

Triage Dependabot vulnerability alerts and propose verified non-breaking dependency version bumps.

24.2k|4.1k|Updated Dec 3, 2022
One-click install
npx skills add https://github.com/activepieces/activepieces --skill triage-dependabot-alerts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-dependabot-alerts
Source: https://github.com/activepieces/activepieces/tree/main/.agents/skills/triage-dependabot-alerts
Command: npx skills add https://github.com/activepieces/activepieces --skill triage-dependabot-alerts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Large Dependabot alert backlogs in a monorepo are overwhelming: the same CVE appears once per manifest, installed versions are hard to verify, and blind version bumps risk breaking the build. This Skill turns a raw alert backlog into a deduplicated, review-ready triage report and only proposes dependency bumps that are proven non-breaking through build, lint, and test runs.

Core Features & Use Cases

  • Deterministic alert fetching and deduplication: Pulls open Dependabot alerts via the GitHub API, validates the response, and collapses hundreds of alerts into distinct (package, advisory) units grouped by severity.
  • Lockfile-grounded verdicts: Censuses every installed copy of each vulnerable package from bun.lock and classifies each advisory as AFFECTED, NOT_AFFECTED, NO_FIX_YET, or DEV_ONLY based on actual usage of the vulnerable API.
  • Proven non-breaking fixes: Bumps approved packages in a single batched PR, handles transitive duplicates with flat overrides, and validates with typecheck, build, lint, and tests before proposing anything.
  • Use Case: A maintainer facing 200 open Dependabot alerts asks for triage and receives a summary table of distinct vulnerabilities, per-package reports with reachability analysis, and one PR containing verified safe version bumps.

Quick Start

Triage the open Dependabot alerts for this repository and report which vulnerable packages actually need version bumps.

Frequently Asked Questions about triage-dependabot-alerts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage a large Dependabot alert backlog in a monorepo?

Fetch open alerts with the GitHub API, then deduplicate by package and advisory since the same CVE repeats per manifest. Group by package, verify installed versions against the lockfile, and triage the distinct set rather than raw alerts.

How do I check if a Dependabot vulnerability actually affects my repo?

Read the installed version from the lockfile and compare it against every vulnerable range in the advisory, including all major lines. Then confirm the vulnerable API is actually imported and exercised in your code, not just present as a transitive dependency.

Why does the Dependabot API return a 403 or 404 error?

The token likely lacks the security_events scope needed to read Dependabot alerts. Refresh the token with gh auth refresh -s security_events for OAuth logins, or create a classic PAT with repo and security_events scopes.

Can I force-bump a vulnerable transitive dependency inside a third-party SDK?

Only for same-major-line copies using a flat overrides or resolutions entry, which bun honors. Cross-major bumps inside third-party SDKs cannot be proven non-breaking by your tests, so document them as residuals instead.

What should I do when a dependency has no patched version available?

Produce a risk-acceptance writeup documenting where the vulnerability is reachable and any existing mitigations. Options include accepting the residual risk, patching locally with patch-package or bun patch, or swapping the library.