Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose licensing information to sbom-tool #539

Closed
mauve opened this issue Apr 28, 2023 · 2 comments
Closed

Expose licensing information to sbom-tool #539

mauve opened this issue Apr 28, 2023 · 2 comments
Labels
status:requirements Full requirements are not yet known, so implementation should not be started type:feature Feature (new functionality)

Comments

@mauve
Copy link

mauve commented Apr 28, 2023

From: microsoft/sbom-tool#122

Hi,

I was playing around with sbom-tool and sbom-tool is unable to show any licenses, according to microsoft/sbom-tool#122 that is because sbom-tool relies on this repo to detect dependencies, but the output is missing licensing information.

How tricky is it to add licensing information?

@JamieMagee JamieMagee added status:requirements Full requirements are not yet known, so implementation should not be started type:feature Feature (new functionality) labels Apr 28, 2023
@JamieMagee
Copy link
Member

JamieMagee commented Apr 28, 2023

License information is out of scope for Component Detection right now.

Our team helps maintain another project that gathers license information: https://clearlydefined.io/. It has APIs that allow fetching of license information: https://api.clearlydefined.io/api-docs/.

@JamieMagee JamieMagee added the status:waiting-on-response Waiting on a response/more information from the user label May 17, 2023
@JamieMagee
Copy link
Member

We're closing this as out-of-scope for now. Component Detection is focused on building the dependency graph. This might make more sense in SBOM tool itself.

@JamieMagee JamieMagee removed the status:waiting-on-response Waiting on a response/more information from the user label May 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:requirements Full requirements are not yet known, so implementation should not be started type:feature Feature (new functionality)
Projects
None yet
Development

No branches or pull requests

2 participants