Hi
Playing with the visualization we realized that any elements in the SBOM (i.e. json objects {...} ) that contain the "type": blaaa key are shown as nodes in the graph even when those elements are nested inside other json objects. While types like "externalRefs" and "Relationship" are good to see as own nodes, other elements are just noise and should not be shown, e.g. "PositiveIntegerRange", "DictionaryEntry", ...
I would suggest to stick only to top level json objects in the "@graph" in the SBOM and not show nested ones except for a select few, via some allowlist. Alternatively, a blocklist for "do not create nodes" for these elements might work, too but that is a longer list to begin with.
Regards
Bogdan
Hi
Playing with the visualization we realized that any elements in the SBOM (i.e. json objects
{...}) that contain the"type": blaaakey are shown as nodes in the graph even when those elements are nested inside other json objects. While types like "externalRefs" and "Relationship" are good to see as own nodes, other elements are just noise and should not be shown, e.g. "PositiveIntegerRange", "DictionaryEntry", ...I would suggest to stick only to top level json objects in the "@graph" in the SBOM and not show nested ones except for a select few, via some allowlist. Alternatively, a blocklist for "do not create nodes" for these elements might work, too but that is a longer list to begin with.
Regards
Bogdan