The fix of the below bug involves adding a new flag to the analysis CLI command: --disable-maven-search.
Please add this flag in the CLI guide, and mention in the release notes in the section that mentions MTA-5588 is fixed, that this flag is required.

Description of problem:

Running the analysis of a customer binary aprox. ~130Mb with customer dependencies and third-party dependencies includes on lib folder, we're obtaining diferents results when repeat the same execution. As say as, in first execution I obtain 30 issues, I repeat an ídem execution and obtain 22, I repeart a obtain 20 issues.

 Version-Release number of selected component (if applicable):

I'm checked with mta-cli-7.2.2 and mta-cli-7.3.0, container-mode and containerless-mode. I've repeted with CRC local and OCP instance on demo.redhat.com with MTA Operator 7.2.2 and  7.3.0 and results are random.

How reproducible:

I'm running this command: ./mta-cli analyze --input ../SWSEAR-MP-sicws-0000-257.ear --output ../mta-cli-7.2.2-containerless.out --source websphere --target eap8 --target openjdk21 --target cloud-readiness 

Steps to Reproduce:

1. Execute: ./mta-cli analyze --input ../SWSEAR-MP-sicws-0000-257.ear --output ../mta-cli-7.2.2-containerless.out --source websphere --target eap8 --target openjdk21 --target cloud-readiness 

2. Check the number of issues

3.Execute the same command:  ./mta-cli analyze --input ../SWSEAR-MP-sicws-0000-257.ear --output ../mta-cli-7.2.2-containerless.out --source websphere --target eap8 --target openjdk21 --target cloud-readiness 

4. Check the number of issues

5. Repeat the number of iterations that you like, always obtains differents results.

Actual results:

 Random results, I can't know how to understand the results.

Expected results:

 Obtain the same report always

Additional info:

-