disclosure-tracker

Automating vulnerability disclosure monitoring involves scanning pending advisories, parsing frontmatter for severity and status, computing age, and classifying drafts into escalate, pending, or cleanup categories. This Skill generates daily digests and escalation notifications for security teams.

Tracking aging vulnerability disclosures requires reading draft advisories from memory, computing their age, and cross-checking linked PRs in status logs. The best approach classifies advisories by severity and age thresholds to trigger automated escalation alerts and daily summaries.

Classifying draft vulnerability advisories requires parsing YAML frontmatter or content to extract repo, severity, status, and title. By computing advisory age, you can categorize drafts into escalate, pending, operator-todo, or cleanup states for compliance visibility.

Cross-referencing pending disclosures with pull requests involves checking memory topics and PR status logs for linked entries. This Skill automates that cross-check to determine PR coverage for each advisory, ensuring drafts with open PRs are tracked and reported accurately.

The disclosure tracker parses YAML frontmatter or content directly to extract repo, severity, status, and title fields. If frontmatter is missing, it falls back to parsing content, ensuring draft advisories are classified and aged even without structured metadata.

Escalating pending vulnerability disclosure drafts depends on computed age and severity thresholds. Drafts exceeding defined age limits are classified as escalate, triggering daily notification alerts to security teams, while newer or resolved items remain pending or move to cleanup.