Reviewing the Estimated Completion Time

Static Analysis

Veracode computes the estimated completion time for static scans of applications based on historical delivery times for applications of similar size and language. After initial submission, the estimated completion time is based on the time it took to deliver results for past versions of the application. You can review the estimated completion time for your application on the prescan results page.

The amount of time that it takes to deliver results for a static scan depends on many factors, including the language or platform in which the application was written, the size of the application, and whether the application is being scanned on behalf of a third party.

Note: For Dynamic Analysis and DynamicDS scans, Veracode's completion objective is to publish results within 24 hours of the conclusion of the scan window. Veracode does not guarantee the estimated completion time. The actual completion time is variable.

Large Binaries

Large applications may take additional time to process. The actual processing time can vary by language, platform, and unique behaviors of the submitted code. For example, applications submitted with missing dependencies, or with dependencies compiled without debug symbols, can take longer.

Veracode makes every effort to deliver results in a timely fashion. Therefore, if applications complete analysis sooner than the estimated delivery window, Veracode publishes the results sooner.

Review Estimated Completion Time

The estimated completion time for an application is shown on the prescan results page before the application is submitted, and on the static scan overview page after submission.

On the prescan results page before submission, the estimated completion time is dynamically updated as modules are selected.

You can see the estimated delivery date on the scan overview page after you have submitted the application.