pvr-triage-monitor

Monitor GitHub private vulnerability report triage states and aging.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

pvr-triage-monitor prevents submitted private vulnerability reports from going stale by automatically checking their GitHub advisory lifecycle and surfacing actionable updates.

Core Features & Use Cases

  • Weekly lifecycle monitoring: Polls each tracked PVR’s triage state and detects transitions like triage → draft/published/withdrawn.
  • Aging escalation: Flags advisories stuck in triage for more than 30 days so maintainers can respond or close them.
  • Optional tracking cross-links: Mentions a configured internal tracking issue URL in notifications for easier handoff and accountability.
  • Memory-backed source of truth: Reads pending disclosures from memory/pending-disclosures and writes back frontmatter updates only (no body changes).

Quick Start

Use pvr-triage-monitor to review all pending private vulnerability reports on disk, notify you of triage state changes, and escalate any advisories stuck in triage for over 30 days.

Frequently Asked Questions about pvr-triage-monitor

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

FAQPage Schema
How do I monitor GitHub private vulnerability reports to prevent triage stalling?

To automate private vulnerability report monitoring, track pending disclosures from memory, probe the GitHub Security Advisory API for state transitions, and notify maintainers of changes or aging advisories over 30 days.

How does automated vulnerability triage state detection work with GitHub GHSA?

Vulnerability triage state detection probes the GitHub Security Advisory API to capture lifecycle transitions like triage to draft or published, updating the pending disclosure frontmatter to reflect the current state.

Can I escalate GitHub security advisories that have been pending for over 30 days?

You can escalate advisories by applying aging escalation logic that identifies pending private vulnerability reports stuck in triage for over 30 days and triggers notifications to maintainers for resolution.

Does this vulnerability triage monitor require writing changes to the report body?

No, the monitor requires only reading pending disclosure frontmatter from memory and writing back state updates, leaving the body unchanged while moving resolved advisories into a separate archive.

What is the best way to track GitHub private vulnerability reports in an autonomous security workflow?

The best way is running a weekly autonomous security workflow that reads pending disclosures from memory, queries the GitHub Security Advisory API for state updates, and dispatches notifications via a runner.