cve-watchlist-action-recommendation-generator

Solid

Generate prioritized CVE watchlists and actionable security recommendations for repositories. Use when analyzing CVE scan results, creating security reports, prioritizing vulnerability remediation, or generating security gate reports for CI/CD. Takes CVE scan results (JSON/SARIF from npm audit, pip-audit, Snyk), reachability analysis, and cutoff date as input. Combines severity, reachability, exploitability, and dependency criticality to rank CVEs by practical risk. Outputs markdown reports with concrete next-step guidance (immediate upgrade, monitor, ignore with justification, apply mitigation) suitable for issue trackers, security reviews, and CI security gates.

Data & Documents 160 stars 17 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 87/100

Stars 20%
73
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# CVE Watchlist & Action Recommendation Generator Generate prioritized CVE watchlists with actionable security recommendations for development and security teams. ## Workflow ### 1. Gather Input Data Collect required inputs: **Required:** - Repository name/path - CVE scan results (JSON/SARIF format from npm audit, pip-audit, Snyk, etc.) - Cutoff date (YYYY-MM-DD) for filtering new CVEs **Optional but recommended:** - Reachability analysis results (which vulnerable code paths are actually used) - Exploit intelligence data (CISA KEV, ExploitDB) - Dependency criticality ratings (how critical each dependency is) **Parse scan results:** ```bash python scripts/parse_scan_results.py scan_results.json auto 2024-01-01 > parsed_cves.json ``` ### 2. Calculate Risk Scores Combine multiple risk factors to prioritize CVEs: ```bash python scripts/calculate_risk_score.py parsed_cves.json reachability.json exploits.json criticality.json > scored_cves.json ``` **Risk scoring formula:** ``` Risk Score = (Severity × 0.35) + (Reachability × 0.30) + (Exploitability × 0.20) + (Dependency Criticality × 0.15) ``` See [risk_scoring.md](references/risk_scoring.md) for detailed methodology. ### 3. Generate Recommendations For each CVE, determine appropriate action based on risk score and context: **Decision tree:** - Risk ≥ 80 (Critical) → Immediate upgrade (24-48h) - Risk 60-79 (High) → Upgrade within days (3-5 days) - Risk 40-59 (Medium) → Next maintenance cycle (2-4 weeks) - Risk 20-39...

Details

Author
ArabelaTso
Repository
ArabelaTso/Skills-4-SE
Created
6 months ago
Last Updated
today
Language
Python
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category