Skip to content

Commit

Permalink
Clarify sentence about last_affected and fixed in docs.
Browse files Browse the repository at this point in the history
Signed-off-by: Tieg Zaharia <tieg.zaharia@gmail.com>
  • Loading branch information
tiegz authored Nov 7, 2024
1 parent 00aefbd commit dff23c1
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/schema.md
Original file line number Diff line number Diff line change
Expand Up @@ -830,8 +830,8 @@ Only **a single type** (either `introduced`, `fixed`, `last_affected`,
`limit`) is allowed in each event object. For instance,
`{"introduced": "1.0.0", "fixed": "1.0.2"}` is **invalid**.

Entries in the `events` array can contain either `last_affected` or `fixed`
events, but not both. It's **strongly recommended** to use `fixed` instead of
An events array can have entries containing either "last_affected" or "fixed" events,
but not both. It's **strongly recommended** to use `fixed` instead of
`last_affected` where possible, as it precisely identifies the version which
contains the fix. `last_affected` should be thought of as the hard ceiling
of the vulnerability _at the time of publication_ in the absence of a fixed version.
Expand Down

0 comments on commit dff23c1

Please sign in to comment.