security-vulnerability-report

Aggregate GitHub Dependabot, code scanning, and secret scanning alerts into prioritized vulnerability reports.

392|73|Updated Jun 12, 2025
One-click install
npx skills add https://github.com/cnoe-io/ai-platform-engineering --skill security-vulnerability-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-vulnerability-report
Source: https://github.com/cnoe-io/ai-platform-engineering/tree/main/ui/src/skills/security-vulnerability-report
Command: npx skills add https://github.com/cnoe-io/ai-platform-engineering --skill security-vulnerability-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Repositories across organizations accumulate security alerts that are difficult to consolidate and act upon. This Skill aggregates Dependabot alerts, code scanning results, and secret scanning findings to deliver a unified, prioritized vulnerability report for quicker remediation.

Core Features & Use Cases

  • Dependabot Alerts: Retrieve open, dismissed, and fixed alerts across repositories with CVE identifiers and severity.
  • Code Scanning Results: Collect rules, descriptions, severities, affected files, and tooling (e.g., CodeQL) for prioritized triage.
  • Secret Scanning: Detects exposed secrets, affected files, and whether remediation has been applied.
  • Cross-Repo Prioritization: Deduplicate shared dependencies and rank risks by severity and exploitability.
  • Customizable Reporting: Produce a concise, executive-ready report with recommended fixes and owners.

Quick Start

Run the security-vulnerability-report skill against your configured GitHub organizations to generate a prioritized vulnerability report.

Frequently Asked Questions about security-vulnerability-report

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

FAQPage Schema
How do I consolidate GitHub security alerts across multiple repositories?

Consolidate GitHub security alerts by collecting Dependabot alerts, code scanning results, and secret scanning findings across repositories into a unified vulnerability report. This process deduplicates shared dependencies and prioritizes risks by severity and exploitability for quicker remediation.

What is the best way to prioritize Dependabot and code scanning vulnerabilities by CVSS score?

Prioritize Dependabot and code scanning vulnerabilities by applying known CVSS scoring to rank risks by severity and exploitability. This approach deduplicates shared dependencies across repositories and produces an executive-style report with recommended fixes.

Can I generate an executive report for exposed secrets and code scanning findings?

Generate an executive report for exposed secrets and code scanning findings by aggregating secret scanning data and code scanning rules. The output includes affected files, remediation status, severities, and recommended fixes formatted for executive review.

Does this vulnerability reporting approach work with multi-repo inputs and GitHub data sources?

This vulnerability reporting approach supports multi-repo inputs and requires integration with GitHub data sources. It retrieves open, dismissed, and fixed alerts with CVE identifiers across configured GitHub organizations to produce a comprehensive vulnerability summary.

Why should I aggregate security alerts instead of checking each repository individually?

Aggregating security alerts solves the problem of scattered vulnerabilities that are difficult to act upon. It deduplicates shared dependencies across repositories, applies cross-repo prioritization using CVSS scores, and delivers a unified report with recommended fixes and owners for faster remediation.

How do I include secret scanning remediation status in a cross-repo security report?

Include secret scanning remediation status in a cross-repo security report by collecting exposed secrets data, affected files, and whether remediation has been applied. This data is aggregated alongside Dependabot and code scanning results to produce a prioritized executive-style report.