> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zdlake.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Advisories

> Understand publisher security notices, affected software claims, and remediation context.

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

| Related concept | What the relationship explains |
| - | - |
| [Vulnerability](https://docs.zdlake.com/concepts/vulnerabilities.md) | Which security issue the notice describes. |
| [Software](https://docs.zdlake.com/concepts/software.md) | Which products or release lines are named by an affected assertion. |
| [Weakness](https://docs.zdlake.com/concepts/weaknesses.md) | The underlying flaw class named by the publisher. |
| [Attack pattern](https://docs.zdlake.com/concepts/attack-patterns.md) | Relevant attacker behavior when supported by source evidence. |

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](https://docs.zdlake.com/concepts/security-data-model.md) for relationship cardinalities.

## Schema

Every advisory detail response starts with these fields:

| Field | Meaning |
| - | - |
| `entity` | Always `advisory`. |
| `entity_id` | Durable Zero identifier for the entity. |
| `id` | Preferred advisory identifier, such as a GHSA or vendor advisory key. |
| `aliases` | Other identifiers associated with the same notice. |
| `title` | Human-readable advisory title. |
| `summary` | Normalized advisory description. |
| `state` | Current lifecycle state of the entity. |
| `published_at` | Publisher release time when available. |
| `source_updated_at` | Most recent relevant publisher update time. |
| `updated_at` | Time Zero last updated the entity. |
| `revision_id` | Identifier for the normalized revision returned by the request. |

Request optional projections when you need more detail:

| Projection | Contents |
| - | - |
| `overview` | Resolution, key fixed releases, and advisory-specific aliases. |
| `affected_targets` | Software identities, affected ranges, fixed versions, and supporting product coordinates. |
| `affected_releases` | Credits and source-specific release metadata retained from the advisory. |
| `software_releases` | Up to 100 current registry-observed releases connected to the advisory, ordered by ecosystem-correct version semantics. The nested assessment is filtered to this advisory and includes source aggregation, conflict state, and explicit truncation metadata. |
| `relationships` | Related entities grouped by type, including direction and supporting sources. |
| `provenance` | Field-level and affected-target evidence keyed by normalized paths. |

Search responses are intentionally more compact than detail responses. Use the API pages for the complete request and response schemas.

## API pages

| Page | Use it for |
| - | - |
| [Search advisories](https://docs.zdlake.com/advisories/search.md) | Search and filter advisory records. |
| [Get an advisory](https://docs.zdlake.com/advisories/get.md) | Retrieve one advisory and request optional projections. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.