/registry

name: registry
description: "Query or update the research registry. Usage: /registry [query]. Examples: /registry stats, /registry check lodash, /registry list in-progress."

/registry [query]

Query or display information from the CVE research registry.

Subcommands

/registry (no arguments)

Display a summary of the registry:

REGISTRY SUMMARY

In Progress:    <count> targets
Submitted:      <count> findings (<count> with CVE IDs)
False Positives: <count>
Skipped:        <count>
Duplicates:     <count>

Total investigated: <sum>
Success rate: <submitted / total investigated>%
False positive rate: <false positives / total investigated>%

/registry stats

Detailed statistics:

REGISTRY STATISTICS

By severity:
  CRITICAL: <count>
  HIGH:     <count>
  MEDIUM:   <count>
  LOW:      <count>

By channel:
  GitHub Advisory: <count>
  HackerOne:      <count>
  Direct email:   <count>

By status:
  Assigned CVE:    <count>
  Awaiting triage: <count>
  Rejected:        <count>

By vulnerability type:
  <type>: <count>
  <type>: <count>
  ...

Recent activity (last 7 days):
  <date> | <action> | <target>
  ...

/registry check <package>

Check if a specific package has been investigated:

1. Search REGISTRY.md for the package name 2. Query OSV.dev for existing CVEs 3. Report status: IN_PROGRESS / SUBMITTED / FALSE_POSITIVE / SKIP / DUPLICATE / CLEAN

/registry list <section>

List all entries in a specific section:

• `/registry list in-progress` - Show all targets currently being investigated
• `/registry list submitted` - Show all submitted findings
• `/registry list false-positives` - Show all false positives with reasons
• `/registry list skip` - Show all skipped targets
• `/registry list duplicate` - Show all duplicates with existing CVE IDs

/registry add <package> <section>

Manually add an entry to the registry. Prompts for required fields based on the section.

/registry move <package> <from-section> <to-section>

Move an entry between sections. Used when status changes (e.g., IN_PROGRESS -> SUBMITTED).

Implementation

Read REGISTRY.md, parse the markdown tables, and present the requested information. For updates, use the Edit tool to modify REGISTRY.md in place.