Vuln Tracker

Audits lifecycle status of security PRs and disclosure drafts produced by vuln-scanner on GitHub.

Updated May 25, 2026
One-click install
npx skills add https://github.com/Cbowcrptex/CBOWCRYPTEX --skill vuln-tracker-cbowcrptex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Vuln Tracker
Source: https://github.com/Cbowcrptex/CBOWCRYPTEX/tree/main/skills/vuln-tracker
Command: npx skills add https://github.com/Cbowcrptex/CBOWCRYPTEX --skill vuln-tracker-cbowcrptex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security disclosure PRs opened by an automated scanner rot silently: merged fixes go uncelebrated, maintainer questions go unanswered, and queued drafts past their disclosure window vanish. This Skill runs a daily sweep that cross-references scan history against live GitHub state so nothing falls through the cracks. ## Core Features & Use Cases - Lifecycle auditing: Cross-references memory/vuln-scanned.json with live GitHub PR state via gh CLI to categorize every disclosure as merged, needs-answer, stale, queued, newly-actionable, and more. - Stars Secured metrics: Aggregates stargazer counts across every repo where fixes landed, are in flight, or are tracked, producing a leaderboard dashboard in memory/topics/vuln-followup.md. - Channel re-probing: Re-checks skipped disclosures to detect when private vulnerability reporting or SECURITY.md becomes available, surfacing newly-actionable items. - Use Case: A maintainer comments on a bot-opened security PR asking for clarification. The next daily run flags it in the operator-action queue and sends a notification with the comment excerpt. ## Quick Start Run the vuln tracker to audit all open security PRs and queued disclosures, then update the follow-up dashboard and notify me of anything needing action.

Frequently Asked Questions about Vuln Tracker

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

FAQPage Schema
How do I track the status of automated security PRs on GitHub?▼

Use gh search prs filtered by the bot author and the fix(security): title prefix, then run gh pr view on each open PR to check reviews, comments, and merge state. Cross-reference results against your scan history JSON to categorize each item.

How to detect maintainer comments that need a reply on bot PRs?▼

Fetch each PR with gh pr view and compare comment authors against the bot account. Any comment from a non-bot author posted after the bot's last comment, or a CHANGES_REQUESTED review decision, counts as needing an answer.

Does this work without a vuln-scanned.json history file?▼

Yes, partially. If the JSON is missing the run exits cleanly, but bot-authored PRs can still be recovered via gh search prs with the title prefix and marked as pre-history entries with severity inferred from titles.

What GitHub permissions are required for vulnerability tracking?▼

A GH_TOKEN or GITHUB_TOKEN with repo scope is sufficient for reading PRs, comments, star counts, and the private-vulnerability-reporting endpoint. All access goes through the gh CLI, which handles authentication internally.

When does the tracker skip sending notifications?▼

Notifications are skipped when there are zero needs-answer items, zero newly-actionable channels, and no items transitioned to merged, closed, stale, or aging states since the previous run's dashboard.