generate-cve-json

To generate a CVE JSON record, you provide a GitHub tracking issue body and the tool extracts standard fields to output a ready-to-paste CVE 5.x envelope for Vulnogram. This eliminates manual data entry for vulnerability disclosures.

Automating CVE 5.x JSON creation is best handled by parsing tracker issues directly into a deterministic JSON document. This approach ensures outputs can be re-generated consistently for reliable diffs and security audits without manual formatting.

Yes, you can include multiple credits and references when generating a CVE JSON file. The tool supports adding multiple reporter and remediation developer credits, alongside multiple references such as pull requests and advisory URLs.

You do not need external dependencies to create deterministic CVE JSON. The tool relies only on the Python standard library and the GitHub CLI for live data access, ensuring reproducible results without complex environment setups.

Deterministic JSON generation helps with security audits by producing identical output for the same input data. This allows security teams to accurately diff records over time and verify changes without manual review noise.

Yes, you can use GitHub CLI data to populate Vulnogram CVE records. The tool accesses live tracker issue data via the GitHub CLI and formats it into a paste-ready JSON envelope compatible with Vulnogram.