-
Notifications
You must be signed in to change notification settings - Fork 358
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
-c param (confidence) is now required to get matches. #480
Comments
Fixes case sensitivity of Enum based arguments Fixes default Confidence argument not being respected Fixes severity not being respected Fixes custom rules not being validated if provided as a directory Adds new option to skip validation of custom rules Adds a TextContainer based API for analyze.
Thanks for the report. I have a fix for the case insensitive enums. I also have a fix for the default behavior - I had missed adding a default value for the commandlineparser. I believe I've identified one additional potential problem, when custom rules were specified as a folder they were not verified before running, just added to the ruleset. I hope to merge all these fixes today. #481 This will come as 1.6.2-beta I believe. 1.6 will be in beta for a short time, I'm currently working on some of the lib APIs, but there are no changes currently planned for the CLI. |
Hello @gfs , When do you plan to release a 1.6 non-beta version with this issue? Thanks in advance. |
I plan to remove the beta flag this week. |
@ismadirolas 1.6.17 (not beta) is now available. |
Describe the bug
In 1.4.x versions, -c param is optional with default value "medium,high", but we have noticed that in 1.5.x versions is mandatory to get any match (we tested it with custom rules only)
By the way, there is a breaking change between 1.4.x and 1.5.x and now the -c values must be with uppercase (before -c 'low,medium.high', now -c 'Low,Medium,High'), so maybe you should update the wiki, or accept both.
To Reproduce
Steps to reproduce the behavior:
ApplicationInspector.CLI analyze -s . -g **/rulesFolder/**,**/.github/actions/**,**/node_modules/**,**/.git/**,**/target/**,*.mock*,*.jpg,*.png,*.gif,*.woff,*.woff2,*.svg,*.ttf,*.jar,*.car,*.war,*.zip,*.a,*.xc*,KakaoOpenSDK,AkamaiBMP,**/dist/** -f json --processing-timeout 600000 --file-timeout 60000 -o result.json -A -u --no-show-progress -r /rulesFolder/ -i -M 20
-> 0 matchesApplicationInspector.CLI analyze -s . -g **/rulesFolder/**,**/.github/actions/**,**/node_modules/**,**/.git/**,**/target/**,*.mock*,*.jpg,*.png,*.gif,*.woff,*.woff2,*.svg,*.ttf,*.jar,*.car,*.war,*.zip,*.a,*.xc*,KakaoOpenSDK,AkamaiBMP,**/dist/** -f json --processing-timeout 600000 --file-timeout 60000 -o result.json -A -u --no-show-progress -r /rulesFolder/ -i -M 20 -c Low,Medium,High
-> X matchesExpected behavior
If we don't pass -c param to CLI, get matches of rules with confidence medium and high.
Operating Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: