Skip to content

Conversation

@clavedeluna
Copy link
Contributor

We need to gather as much finding metadata as possible. Implemented finding_msg for codeql, remaining tools as TODO

return result_set


# TODO: cache, make hashable
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have a ton of bandwidth so left it as a todo, since we're passing dict of lists and some other unhashable data here, it's not super fast to do, but we should do it at some point

@sonarqubecloud
Copy link

sonarqubecloud bot commented Dec 3, 2024

Quality Gate Passed Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

Copy link
Member

@drdavella drdavella left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@clavedeluna I believe the need for this metadata exists not at the finding level but at the rule level. It's possible that we should expose this at the level of SarifResultSet as a mapping between rule IDs and metadata.

@clavedeluna clavedeluna closed this Dec 4, 2024
auto-merge was automatically disabled December 4, 2024 20:42

Pull request was closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants