fix(coverity-api): add support for RESOURCE_LEAK quality findings#14749
Merged
Conversation
Extend the Coverity API parser to import findings with checker RESOURCE_LEAK and displayIssueKind Quality, in addition to the existing Security findings. Update tests to reflect the new counts and add assertions covering RESOURCE_LEAK field values. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
valentijnscholten
approved these changes
Apr 27, 2026
Maffooch
approved these changes
Apr 29, 2026
paulOsinski
approved these changes
Apr 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
[sc-12941]
Summary
RESOURCE_LEAKfindings wheredisplayIssueKindisQuality, in addition to the existingSecurityfindingsQualitycheckers (e.g.NULL_RETURNS,FORWARD_NULL) remain excludedRESOURCE_LEAKfindings are parsed with the same fields as security findings:title,severity,cwe,file_path,date,unique_id_from_tool,nb_occurences,active/verifiedTest plan
few_findings.json,few_findings_triaged_as_bug.json, andfew_findings_mitigated.jsonRESOURCE_LEAKfinding fields (title, severityHigh, CWE 404, file path, date, active/verified state)only_non_resource_leak_quality.json(NULL_RETURNS/FORWARD_NULL only) so thetest_parse_only_qualitytest continues to assert 0 findings for non-RESOURCE_LEAK quality checkers🤖 Generated with Claude Code