pvr-triage-monitor

You can monitor private vulnerability reports by scanning memory/pending-disclosures to track PVR lifecycles across triage, draft, published, and withdrawn states, generating notifications for any state transitions or maintainer responses.

Automating triage for private vulnerability reports involves loading pending disclosures from memory and tracking their GitHub advisory state to detect maintainer acceptance or rejection and produce concise notifications.

Detecting aging vulnerability reports requires scanning pending disclosures to flag triage items older than 30 days with no maintainer response, allowing you to surface action items for escalation or closure.

Updating YAML frontmatter during GitHub advisory state changes involves enforcing required fields and automatically adding last_checked and resolved_at timestamps when applicable during lifecycle monitoring.

Tracking private vulnerability report lifecycles is best handled by polling the GitHub advisory state, detecting transitions between triage and published phases, and linking optional patch branches to surface required actions.

Private vulnerability report monitoring works without external dependencies by loading pending disclosures directly from memory and comparing PVR states internally to generate concise lifecycle change notifications.