What is a scannable module?

Every scan with Veracode Static Analysis is comprised of two parts:

1. Pre-scan (typically takes 5 to 10 minutes), which results in a module selection 
2. Analysis, which results in the actual flaws

In the pre-scan, it analyzes your upload for what we call Scannable Modules.
A loose definition:
 

"A collection of inter-dependent files, scannable as one independent unit, optionally identified by a potentially user-facing entry point."

When we analyze the upload of static languages, we will typically create several modules of either of the following categories:

1. A top-level module, our heuristics have determined that this may be user-facing. Typically means this group of files with this entry point does not have anything call into it.
2. A dependency module, hidden by default in our UI, this file or groups of files are called by other files in the upload.