Data models

Every document Vulners returns is a bulletin, modelled in three inheritance layers so you get typed fields and IDE hints at whatever level of detail you need:

1. Bulletin — the base: the fields every document carries.
2. Family models (CveBulletin, ExploitBulletin, …) — one per bulletinFamily, extending Bulletin with that family's shared fields.
3. Collection models — one per collection type, extending its family model with the fields specific to that collection.

search/archive/audit return the most specific model that matches a document's type, then its bulletinFamily, then Bulletin. Every model keeps extra="allow", so a field Vulners adds before the SDK models it is still there on the object, just untyped — nothing is ever dropped.

A field sits at the level where it is always present: on Bulletin when every document carries it, on a family model when every document of that bulletinFamily carries it, otherwise on the collection model.

Structure

Bulletin (base) → a model per bulletinFamily → a model per collection type. Every family model extends Bulletin; every collection model extends its family model, so isinstance holds at every level (a nessus document is a NessusBulletin, which is a ScannerBulletin, which is a Bulletin). Each family below links to its page, which lists the family's fields and every collection type under it.

• Bulletin — base fields, common to every document
  • BlogBulletin — bulletinFamily: blog
  • BugbountyBulletin — bulletinFamily: bugbounty
  • CnnvdBulletin — bulletinFamily: cnnvd
  • CnvdBulletin — bulletinFamily: cnvd
  • CryptoBulletin — bulletinFamily: crypto
  • CveBulletin — bulletinFamily: cve
  • EuvdBulletin — bulletinFamily: euvd
  • ExploitBulletin — bulletinFamily: exploit
  • InfoBulletin — bulletinFamily: info
  • JvnBulletin — bulletinFamily: jvn
  • LibraryBulletin — bulletinFamily: library
  • MicrosoftBulletin — bulletinFamily: microsoft
  • NcscBulletin — bulletinFamily: ncsc
  • NozomiBulletin — bulletinFamily: nozomi
  • ScannerBulletin — bulletinFamily: scanner
  • SoftwareBulletin — bulletinFamily: software
  • ToolsBulletin — bulletinFamily: tools
  • UnixBulletin — bulletinFamily: unix

Base fields

Present in every document, at the Bulletin level — full table with types, descriptions and examples on the base page:

bulletinFamily, cvelist, cvss, cvss2, cvss3, cvss4, description, enchantments, epss, href, id, immutableFields, lastseen, metrics, modified, published, references, reporter, sourceAvailable, timestamps, title, type, vendorId, vhref, viewCount