CVE-VALIDATE(1)

💖 CVE-VALIDATE(1) 💖

okay so bestie, welcome to the cve validate manual page — yes that's the manual name, it's literally called the cve validate Manual, we love a self-titled moment 👑

---

✨ NAME ✨

cve-validate — validate a CVE record against the 5.1.1... 👀 (yes the name in the original just trails off like that, it's giving mysterious main character energy, no cap)

---

🌸 SYNOPSIS 🌸

cve validate [OPTIONS]

that's it. that's the whole vibe. you run it, you give it options, it validates. iconic.

---

🦋 DESCRIPTION 🦋

so basically, cve-validate validates a CVE record against the 5.1.1 CVE JSON (sub)schema. that's the whole job. it takes your CVE record, it checks it against the schema, and it tells you if it's slaying or if it's a mess. periodt. 💅

---

🎀 OPTIONS 🎀

• -j, --cve-json TEXT — the actual JSON body of the CVE record, passed in as text. like, right there, inline, no file needed. just raw JSON energy ✨
• -f, --cve-json-file FILENAME — a file that contains the JSON body of a CVE record. same thing as -j basically but you're handing it a FILENAME instead of the JSON itself, because sometimes your JSON is long and you don't wanna paste it into your terminal like a menace 🫶
• -s, --schema-type [full|cna-published|cna-rejected|adp] — the specific type of schema you wanna validate against. your choices are literally full, cna-published, cna-rejected, or adp. pick your fighter 🥊 and the default? it's cna-published, so if you don't say anything, that's the one you get 💖

ngl the original text wraps that default across two lines as cna-published — same thing, don't let the line break gaslight you bestie 😭

---

and that's the whole page!! short, sweet, efficient, highkey a bop 🌈

cve validate Manual · version 1.8.0 · dated 2025-09-29 — shoutout to whoever wrote this, you ate and left no crumbs, mwah 💋 🎀✨🦋💖