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
We are running syft to generate sbom files with [email protected] output option.
We are seeing escaped characters in some sections of the SBOM structure like "bom-ref" and others.
When the SBOM.json is created, the Contents and its bom-ref information shows escaped characters.
Is this the expected behavior? I tried to search for open issues, tried to update my syft version, check charset, etc.
I was hoping to see the correct module/package name.
See how it looks like when the SBOM is created. Check keys bom-ref, cpe and purl shows escaped and different "patterns" to generate the output, since the name shows it properly.
We are running syft to generate sbom files with [email protected] output option.
We are seeing escaped characters in some sections of the SBOM structure like "bom-ref" and others.
When the SBOM.json is created, the Contents and its bom-ref information shows escaped characters.
Is this the expected behavior? I tried to search for open issues, tried to update my syft version, check charset, etc.
I was hoping to see the correct module/package name.
See how it looks like when the SBOM is created. Check keys
bom-ref
,cpe
andpurl
shows escaped and different "patterns" to generate the output, since thename
shows it properly.Steps to reproduce the issue:
Consider this
package-lock.json
, noticed themodule_name
in the section:Command:
Output:
Environment:
The text was updated successfully, but these errors were encountered: