Fix no filename and filepath in results.json #40
Conversation
This file contains 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
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.
When analysing languages without debug symbols (e.g., dotnet), the Veracode policy findings API does not return filepath and filename information in the findings_details section. This causes the current action to fail because it relies on this information to convert results to sarif.
Solution:
Filtering: The pull request adds logic to filter out policy findings that lack filepath and filename information. This ensures that the action only processes findings that can be accurately reported.
Warning Annotation: A warning annotation has been added to alert users about the potential limitation. This provides a clear indication that findings for languages without debug symbols might have incomplete reporting.