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

Incorporate SCA results into 3rd party check #17

Open
dipsylala opened this issue Jun 24, 2024 · 0 comments
Open

Incorporate SCA results into 3rd party check #17

dipsylala opened this issue Jun 24, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@dipsylala
Copy link
Collaborator

The SCA results can be used to review the 3rd party libraries within third_party.go. These are already pulled back as part of the detailed report, and the existence is used in missing_sca_components.

software_composition_analysis / vulnerable_components / component - the file_name attribute.

If there is a selected top level module that matches the file_name, we can class it as 3rd party alongside the existing list.

There is a chance that the filename will not match due to it being renamed, but this is typically the exception rather than the rule.

Sample Build ID: 34772495

@dipsylala dipsylala added the enhancement New feature or request label Jun 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant