Can I use an exisiting SBOM as input and use scancode to map licence information by scancode's list of aliases? #4235
Replies: 1 comment 1 reply
-
@chess-levin we have a scancode.io pipeline to load SBOMs: https://scancodeio.readthedocs.io/en/latest/built-in-pipelines.html#load-sbom
Yes, we typically detect these correctly using each modules in https://github.com/aboutcode-org/scancode-toolkit/tree/develop/src/packagedcode which has specialized code to handle these different license fields. But this works on scanning manifests, for SBOMs we only load the information present. One option could be to load the SBOMs and then enrich this data from purldb: https://scancodeio.readthedocs.io/en/latest/built-in-pipelines.html#enrich-with-purldb-addon. This downloads the package source, binary and metadata from the package ecosystem repository, scans those using scancode and summarizes the license for that package. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi folks,
I'm looking for a tool, that can enrich the (component) licence information that a SBOM comes with.
I have several SBOMs generated by the SBOM-generator that comes with build management tool (maven, gradle, npm, etc). The "licences" field is "used" very different by each tool (see below).
So I'm looking for a tool that tries to match the given information with a set of aliases. The resulting SBOM should contain at least a valid licence id or an information that it was not possible to match the information with an alias.
I hoped that scancode could help me with this task, but I think there is no option that it reads an exisiting SBOM.
Any help apreciated. Thank you!
Examples:
or
or
or
or
or
or
etc. etc.
Beta Was this translation helpful? Give feedback.
All reactions