When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
More information
.png){kind=logo}
Hi @RBhumula322417 (Community Member) ,
Welcome!
We don't recommend introducing flaws into your application to test Veracode Static Analysis, Veracode Static Analysis is tuned to report true positives as much as possible and many 'test flaws' do not represent real risk (typically they do not take data from outside of the application, so cannot be used by an attacker)
I would recommend reviewing our packaging guide at: https://help.veracode.com/r/compilation_packaging and verifying that your versions are supported and your packaging is per our guidelines.
If you'd like you can also schedule a consultation call wherein you can review your packaging with a member of the Veracode Application Security Consulting service.
You can check out this knowledge article (https://community.veracode.com/s/article/How-to-schedule-a-consultation-call) on how to schedule a consultation call with us.
Thank you,
Boy Baukema