For analysis purposes we separate files in scope into several categories: main, test, generated, deployment and build, and other.
The main category contains all manually created source code files that are being used in the production.
Files in the main category are used as input for other analyses: logical decomposition, concerns, duplication, file size, unit size, and conditional complexity.
Test source code files are used only for testing of the product. These files are normally not deployed to production.
Build and deployment source code files are used to configure or support build and deployment process.
Generated source code files are automatically generated files that have not been manually changed after generation.
While a source code folder may contain a number of files, we are primarily interested in the source code files that are being written and maintained by developers.
Files containing binaries, documentation, or third-party libraries, for instance, are excluded from analysis. The exception are third-party libraries that have been changed by developers.
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
files with any line of content like "//[ ]*Generated by .*".
files with paths like ".*[.](py|java|h|cc|cpp|m|rb|php)" AND any line of content like ".*Generated by the protocol buffer compiler[.][ ]+DO NOT EDIT[!].*".
1784 files match defined criteria (441,620 LOC, 53.0% vs. main code):
483 *.java files (246,576 LOC)
1,096 *.php files (130,475 LOC)
146 *.txt files (24,231 LOC)
25 *.py files (12,429 LOC)
10 *.cpp files (12,342 LOC)
14 *.rb files (8,320 LOC)
10 *.h files (7,247 LOC)
" *.java" is biggest, containing 55.83% of LOC.
" *.h" is smallest, containing 1.64% of LOC.
Build and Deployment Code
Source code used to configure or support build and deployment process.