cna-match

Match GitHub repositories to CVE Numbering Authorities and output report.json.

Updated May 20, 2026
One-click install
npx skills add https://github.com/lukehinds/scrutineer-attest-test --skill cna-match
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cna-match
Source: https://github.com/lukehinds/scrutineer-attest-test/tree/main/skills/cna-match
Command: npx skills add https://github.com/lukehinds/scrutineer-attest-test --skill cna-match

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Determine which CVE Numbering Authority (CNA) covers this repository, so disclosures can be routed to the CNA's security contact rather than only the maintainer. It reads scrutineer's cached CNA list and matches the repository owner, project name, and published packages against each CNA's published scope.

Core Features & Use Cases

  • Identify the CNA that governs a repository based on owner, repository name, and published package scopes.
  • Generate a report.json containing the matched CNA and rationale, for audit and escalation.
  • Handle repositories with no CNA coverage by routing disclosures to the maintainer and documenting the reasoning for follow-up with external CNAs if applicable.

Quick Start

Run the cna-match skill on a repository to generate a CNA coverage report.

Frequently Asked Questions about cna-match

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

FAQPage Schema
How do I find the correct CVE Numbering Authority for a GitHub repository?

To find the correct CVE Numbering Authority for a GitHub repository, match the repository owner, project name, and published package scopes against CNA entries to route security disclosures to the proper contact.

What happens when no CVE Numbering Authority covers a repository for vulnerability disclosure?

When no CVE Numbering Authority covers a repository, the disclosure is routed to the maintainer as a fallback, and the reasoning is documented for potential follow-up with external CNAs.

Can I match published package scopes to CNA entries for security compliance?

Yes, you can match published package scopes to CNA entries by comparing repository metadata against each CNA's defined scope to identify the governing authority for compliance and disclosure.

How do I generate a CNA coverage report for repository analysis?

You generate a CNA coverage report by running an analysis that reads the cached CNA list, compares repository metadata, and outputs a report.json file containing the matched CNA and a concise rationale.

What is the best way to route security disclosures for GitHub-hosted projects?

The best way to route security disclosures for GitHub-hosted projects is to identify the governing CNA based on repository owner and package scopes, directing vulnerability reports to the assigned security contact.