Skip to main content
Advisories are normalized security notices from ecosystem databases, vendors, and coordinated disclosure sources. They preserve the identity and timing of a publisher’s notice while connecting its claims to vulnerabilities and affected software. Use an advisory when the notice itself matters: affected versions, fixed releases, publisher guidance, publication timing, or the original disclosure. Software is represented as a versionless product. For supported packages, registry-observed release children can be assessed against an advisory’s normalized affected ranges while preserving the advisory as the source of the affected-version claim.

When to use advisories

  • Understand what a publisher says is affected and which releases contain a fix.
  • Connect software security notices to vulnerabilities and weaknesses.
  • Compare notices from different publishers that describe the same issue.
  • Follow a normalized claim back to the publisher’s original record.
Publisher claims can disagree or describe different product scopes. Treat normalized advisory data as a navigable summary and use provenance when exact source wording or evidence matters.

Relationships

An advisory-to-software relationship does not mean every release is affected. Inspect the affected assertion, version ranges, and fixed versions before using the relationship for remediation. See Security data model for relationship cardinalities.

Schema

Every advisory detail response starts with these fields: Request optional projections when you need more detail: Search responses are intentionally more compact than detail responses. Use the API pages for the complete request and response schemas.

API pages