-
Notifications
You must be signed in to change notification settings - Fork 19
Issues: openvex/spec
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Ability to include vuln information: Severity, CVSS Score, CVSS Attack Vector, etc.
#49
opened Nov 14, 2024 by
grokify
Clarification on Use of @id, PURL Identifier, and Impact Statements
question
Further information is requested
#48
opened Jun 24, 2024 by
nikosgalanis
Storing VEX files in a dedicated directory within Git repositories
#46
opened May 1, 2024 by
knqyf263
Use Cases
documentation
Improvements or additions to documentation
good first issue
Good for newcomers
#36
opened Aug 14, 2023 by
puerco
Modify severity
area/vulnerability
Issues and PRs related to the vulnerability field
#31
opened Jun 22, 2023 by
itaysk
Update Spec to point out New feature or request
@id
change
enhancement
#29
opened Jun 15, 2023 by
tschmidtb51
Version ranges in product_id/subcomponent_id
area/product
Issues and PRs related to the product field
#26
opened Jun 4, 2023 by
knqyf263
Product identifiers with CycloneDX
area/product
Issues and PRs related to the product field
#23
opened Apr 17, 2023 by
knqyf263
Products
not listed as required
area/product
#19
opened Feb 9, 2023 by
tschmidtb51
ProTip!
Add no:assignee to see everything that’s not assigned.