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
Thanks for the report! This is indeed a problem of the tag-value parser. With the colon within the version the parser assumes that a new tag value pair starts. But as this is not specified in the spec otherwise and should be valid, this is clearly a bug and I will fix this.
While applying sbomqs quality checks on SBOMs, we found the parser failing to parse versions with ":" in them
results in the attached file with the missing field -
However, the included versions is indeed
This is not an issue for spdx-json because of the quotes.
What did you expect to happen?
Accept the valid versions correctly.
What happened instead?
bom.nginx.spdx.txt
parser considers the SBOM invalid
Additional details (base image name, container registry info...):
The text was updated successfully, but these errors were encountered: