Vuln Tracker

Audits vuln-scanner security PR and disclosure lifecycle status against live GitHub data.

626|225|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/aaronjmars/aeon --skill vuln-tracker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Vuln Tracker
Source: https://github.com/aaronjmars/aeon/tree/main/skills/vuln-tracker
Command: npx skills add https://github.com/aaronjmars/aeon --skill vuln-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Vuln Tracker prevents security disclosures and PRs created by vuln-scanner from silently rotting by auditing their daily lifecycle state and surfacing anything that needs operator attention.

Core Features & Use Cases

  • Daily audit of scan outputs: Cross-references vuln-scanner history with live GitHub state to identify merged-but-not-aggregated wins, maintainer questions needing replies, and PRs that are too old to remain unattended.
  • Coverage repair via GitHub search: Detects gaps where prior scan history may not include older bot PRs, then backfills by searching bot-authored security PRs for reliable lifecycle reporting.
  • Operational dashboard updates: Rewrites the operator-facing memory/topics/vuln-followup.md dashboard with updated Stars Secured metrics and categorized queues (needs answer, newly actionable, stale/aging, queued, closed without merge, and more).

Quick Start

Ask your autonomous agent to run the Vuln Tracker daily to update memory/topics/vuln-followup.md and produce an operator notification only when there is meaningful movement or actionable items.

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 lifecycle status of security pull requests across multiple repositories?

Vuln Tracker audits security PR lifecycle status by reconciling saved scan history with current GitHub pull request state. It categorizes merged outcomes, maintainer response gaps, and stale openings across multiple repositories to surface actionable items.

Why do my security vulnerability disclosures and PRs go stale without warning?

Security disclosures go stale when they lack continuous lifecycle auditing. Vuln Tracker prevents silent rot by cross-referencing vuln-scanner history with live GitHub state to detect aging PRs and maintainer questions needing immediate replies.

How do I automate daily monitoring of GitHub vulnerability advisories and bot PRs?

Automate daily monitoring by running Vuln Tracker to deterministically re-probe GitHub pull request and advisory state. It backfills missing scan history by searching bot-authored security PRs and rewrites an operational dashboard with categorized queues.

Do I need authenticated GitHub CLI access to audit vulnerability management workflows?

Yes, you need authenticated GitHub CLI access via GH_TOKEN to audit vulnerability management workflows. Vuln Tracker requires this token to perform deterministic re-probing, categorization, and dashboard rewrite logic across your repositories.

What's the best way to maintain a compliance dashboard for security operations?

Maintain a compliance dashboard by rewriting the operator-facing vuln-followup.md file with updated metrics. Vuln Tracker updates Stars Secured metrics and categorizes queues like needs answer, newly actionable, stale, and closed without merge to drive notifications.

How does Vuln Tracker handle skipped or queued vulnerability disclosure conditions?

Vuln Tracker handles queued or skipped disclosure conditions by applying deterministic categorization logic during its daily audit. It reconciles these states against current GitHub advisory data and organizes them into dedicated dashboard queues for operator review.