apple / apple-llvm-infrastructure-tools
Source Code Overview

Analysis scope, overview of main, test, generated, deployment, build, and other code.

Source Code Analysis Scope
Files includes and excluded from analyses
in
cfg
txt
awk
mk
TXT
  • 14 extensions are included in analyses: py, in, h, sh, md, cfg, txt, awk, cpp, json, mk, gitignore, TXT, rst
  • 7 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (1 file).
    • exclude files with path like ".*/docs/.*" (Documentation) (12 files).
    • exclude files with path like ".*/bin/.*" (Binaries for distribution) (2 files).
    • exclude files with path like ".*/git[-]history[.]txt" (Git history) (1 file).
    • exclude files with path like ".*/git[-][a-zA-Z0-9_]+[.]txt" (Git data exports for sokrates analyses) (0 files).
    • exclude files with path like ".*/sokrates_conventions[.]json" (Sokrates scoping conventions) (1 file).
    • exclude files with path like ".*[.]txt" (Text files) (1 file).
Overview of Analyzed Files
Basic stats on analyzed files
Intro
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.

main7604 LOC (74%) 46 files
test1752 LOC (17%) 44 files
generated0 LOC (0%) 0 files
build and deployment837 LOC (8%) 16 files
other27 LOC (<1%) 2 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
txt
awk
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 46 files match defined criteria (7,604 lines of code, 100.0% vs. main code):
    • 19 *.h files (4,733 lines of code)
    • 22 *.py files (1,792 lines of code)
    • 2 *.cpp files (691 lines of code)
    • 1 *.txt files (229 lines of code)
    • 2 *.awk files (159 lines of code)
  • " *.h" is biggest, containing 62.24% of code.
  • " *.awk" is smallest, containing 2.09% of code.


*.h4733 LOC (62%) 19 files
*.py1792 LOC (23%) 22 files
*.cpp691 LOC (9%) 2 files
*.txt229 LOC (3%) 1 files
*.awk159 LOC (2%) 2 files
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
in
cfg
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/test_.*".
    • files with paths like ".*/[Tt]est/.*".
    • files with paths like ".*[-]test[-].*".
    • files with any line of content like ".*/simpletest/.*".
  • 44 files match defined criteria (1,752 lines of code, 23.0% vs. main code):
    • 20 *.py files (1,410 lines of code)
    • 21 *.in files (305 lines of code)
    • 3 *.cfg files (37 lines of code)
  • " *.py" is biggest, containing 80.48% of code.
  • " *.cfg" is smallest, containing 2.11% of code.


*.py1410 LOC (80%) 20 files
*.in305 LOC (17%) 21 files
*.cfg37 LOC (2%) 3 files
Build and Deployment Code
Source code used to configure or support build and deployment process.
mk
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]sh".
    • files with paths like ".*[.]mk".
  • 16 files match defined criteria (837 lines of code, 11.0% vs. main code):
    • 14 *.sh files (802 lines of code)
    • 2 *.mk files (35 lines of code)
  • " *.sh" is biggest, containing 95.82% of code.
  • " *.mk" is smallest, containing 4.18% of code.


*.sh802 LOC (95%) 14 files
*.mk35 LOC (4%) 2 files
Other Code
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]json".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.](rst|rest|resttxt|rsttxt)".
    • files with paths like ".*[.]txt".
  • 2 files match defined criteria (27 lines of code, 0.4% vs. main code):
    • 1 *.md files (18 lines of code)
    • 1 *.json files (9 lines of code)
  • " *.md" is biggest, containing 66.67% of code.
  • " *.json" is smallest, containing 33.33% of code.


*.md18 LOC (66%) 1 files
*.json9 LOC (33%) 1 files
Analyzers
Info about analyzers used for source code examinations.
  • *.h files are analyzed with CppAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Advanced heuristic dependency analysis
  • *.py files are analyzed with PythonAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Basic heuristic dependency analysis
  • *.cpp files are analyzed with CppAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Advanced heuristic dependency analysis
  • *.txt files are analyzed with DefaultLanguageAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Basic code cleaning (empty lines removed for LOC calculations and duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis
  • *.awk files are analyzed with DefaultLanguageAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Basic code cleaning (empty lines removed for LOC calculations and duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis


2022-01-30 21:59