The Veracode platform performs a preliminary analysis, or Pre-Scan, of your binaries to validate that they can be analyzed and to give you an opportunity to fix problems with the uploaded files before submitting your scan request. The results of the Pre-Scan verification are given as messages in the module table; summary information appears as you select modules to be scanned.
During pre-scan, red and orange informational messages will be shown in the status column. Red messages prevent proceeding with scanning the corresponding module only. Orange messages indicate issues that should be corrected to ensure an accurate scan, but which do not block analysis from proceeding. Green messages indicate that all is well with the associated module. If there is a failure Veracode will attempt to provide details on why the failure occurred and how to resolve it.
One example of pre-scan helping to resolve failures is the identification of missing dependencies that are referenced by the uploaded files. The output of the pre-scan will tell you what binaries are missing and will give you the option to upload them. In some cases binaries will need to be uploaded in order to provide a complete picture of the application for analysis. Other times it will be optional to upload the dependency, since the scan can complete without the additional information it provides.
After you resolve a pre-scan warning you will need to resubmit the affected files or libraries to the Veracode platform. If you need to re-upload binaries, or upload new binaries, click the Back or Add Files button, locate the files to be added, and upload them.
You do not need to wait for pre-scan verification to complete, as you will receive an email notification that you can return to the platform to select modules to scan. Refer to the Veracode help center for more information on Pre-scan error messages and application submittal error codes.