Perl analysis with zarn - #1047
Merged
Merged
Conversation
m-1-k-3
marked this pull request as draft
February 22, 2024 14:46
m-1-k-3
added
enhancement
m-1-k-3
marked this pull request as ready for review
February 25, 2024 09:35
Member
Author
|
Base image updated ... will mergen now |
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
1 participant
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.
Feature
No perl code analysis integrated
Using zarn for code analysis - https://github.com/htrgouvea/zarn and https://heitorgouvea.me/2023/03/19/static-security-analysis-tool-perl
Important: This PR needs an update of the EMBA docker base image.
Important: We currently use commit 009331c in the EMBA base image. This results in more accurate line numbers but we are running into a higher false positive rate. See also htrgouvea/zarn#37 (comment)