You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we start to introduce producing VEX documents #591 , there are some input values which are manually curated (e.g. "affected" / "not affected", "justification", "response", etc). There are (at least) two opportunities here:
Provide a way to summarize documents provided as input
Provide a way to add or modify contents (such as indicate "not affected", add a justification, etc) without having the consumer resort to scripting
The text was updated successfully, but these errors were encountered:
FYI: The SPDX SBOM team is working on a V2.3 release that includes the ability for a software vendor to provide a link to a vulnerability report that is independently updated from the static SBOM. The SPDX proposal uses existing ExternalRef capabilities and supports any type of vulnerability report format, i.e.
As we start to introduce producing VEX documents #591 , there are some input values which are manually curated (e.g. "affected" / "not affected", "justification", "response", etc). There are (at least) two opportunities here:
The text was updated successfully, but these errors were encountered: