openvex/spec

Issues

• Consider defining an OpenVEX mediaType

  #34 opened a year ago by sudo-bmitch
  2

• Storing VEX files in a dedicated directory within Git repositories

  #46 opened 6 months ago by knqyf263
  8

• Published schema for OpenVex

  #14 opened 4 months ago by garethr
  8

• Clarification on Use of @id, PURL Identifier, and Impact Statements

  #48 opened 4 months ago by nikosgalanis
  2

• clarifying product identification

  #47 opened 5 months ago by itaysk
  0

• Version ranges in product_id/subcomponent_id

  #26 opened a year ago by knqyf263
  3

• Modify severity

  #31 opened a year ago by itaysk
  6

• Make OpenVEX extensible ?

  #44 opened a year ago by FrancoisLR
  0

• Notifications of new VEX

  #9 opened 2 years ago by pdxjohnny
  3

• Standard for VEX document discovery

  #43 opened a year ago by micahhausler
  1

• README.md needs to be updated to reflect v0.2.0 spec changes

  #42 opened a year ago by frenchi
  1

• Use Cases

  #36 opened a year ago by puerco
  1

• Modify Spec to Require Artifact Digest in PURL

  #10 opened a year ago by tpletcher-hpe
  8

• Diagram missing from ATTESTING.md

  #38 opened a year ago by sudo-bmitch
  0

• Allow for vulnerability to be a list

  #12 opened a year ago by garethr
  7

• More explicit expectations for package identifiers

  #16 opened a year ago by luhring
  2

• VEX schema/spec version should be a field in the metadata

  #20 opened a year ago by lumjjb
  4

• PURL matching with qualifiers

  #27 opened a year ago by itaysk
  3

• Ability to refer back to an SBOM?

  #28 opened a year ago by rnjudge
  4

• Clarify timestamps

  #18 opened a year ago by tschmidtb51
  2

• Update Spec to point out `@id` change

  #29 opened a year ago by tschmidtb51
  1

• timestamp issue

  #30 opened a year ago by tschmidtb51
  2

• Be more specific in the Sample Scenario

  #17 opened 2 years ago by tschmidtb51
  4

• `Products` not listed as required

  #19 opened 2 years ago by tschmidtb51
  4

• Product identifiers with CycloneDX

  #23 opened 2 years ago by knqyf263
  4

• Add "impact_statement" to specification

  #24 opened a year ago by nishakm
  2