bazelbuild / rules_foreign_cc
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
txt
patch
in
ninja
  • 18 extensions are included in analyses: bzl, txt, cpp, h, c, md, patch, sh, xml, cc, yaml, gitignore, py, in, toml, java, ninja, json
  • 8 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (11 files).
    • exclude files with path like ".*/(3rd|[Tt]hird)[-_]?[Pp]arty/.*" (Dependencies) (43 files).
    • exclude files with path like ".*/deps/.*" (Dependencies) (3 files).
    • exclude files with path like ".*/docs/.*" (Documentation) (13 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) (33 files).
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.

main9044 LOC (82%) 40 files
test964 LOC (8%) 9 files
generated0 LOC (0%) 0 files
build and deployment0 LOC (0%) 0 files
other1017 LOC (9%) 82 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 40 files match defined criteria (9,044 lines of code, 100.0% vs. main code):
    • 39 *.bzl files (8,790 lines of code)
    • 1 *.py files (254 lines of code)
  • " *.bzl" is biggest, containing 97.19% of code.
  • " *.py" is smallest, containing 2.81% of code.


*.bzl8790 LOC (97%) 39 files
*.py254 LOC (2%) 1 files
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*_test[.].*".
    • files with paths like ".*/test_.*".
    • files with paths like ".*/[Tt]ests/.*".
    • files with paths like ".*/[Tt]est/.*".
    • files with paths like ".*_tests[.].*".
    • files with any line of content like ".*/simpletest/.*".
  • 9 files match defined criteria (964 lines of code, 10.7% vs. main code):
    • 7 *.bzl files (962 lines of code)
    • 2 *.h files (2 lines of code)
  • " *.bzl" is biggest, containing 99.79% of code.
  • " *.h" is smallest, containing 0.21% of code.


*.bzl962 LOC (99%) 7 files
*.h2 LOC (<1%) 2 files
Other Code
ninja
in
patch
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]json".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/[Ee]xamples/.*".
    • files with paths like ".*[.]patch".
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
  • 82 files match defined criteria (1,017 lines of code, 11.2% vs. main code):
    • 10 *.xml files (271 lines of code)
    • 22 *.cpp files (253 lines of code)
    • 8 *.md files (202 lines of code)
    • 17 *.h files (93 lines of code)
    • 15 *.c files (81 lines of code)
    • 4 *.sh files (35 lines of code)
    • 1 *.ninja files (29 lines of code)
    • 2 *.in files (18 lines of code)
    • 1 *.java files (14 lines of code)
    • 1 *.patch files (13 lines of code)
    • 1 *.cc files (8 lines of code)
  • " *.xml" is biggest, containing 26.65% of code.
  • " *.cc" is smallest, containing 0.79% of code.


*.xml271 LOC (26%) 10 files
*.cpp253 LOC (24%) 22 files
*.md202 LOC (19%) 8 files
*.h93 LOC (9%) 17 files
*.c81 LOC (7%) 15 files
*.sh35 LOC (3%) 4 files
*.ninja29 LOC (2%) 1 files
*.in18 LOC (1%) 2 files
*.java14 LOC (1%) 1 files
*.patch13 LOC (1%) 1 files
*.cc8 LOC (<1%) 1 files
Analyzers
Info about analyzers used for source code examinations.
  • *.bzl 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
  • *.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


2022-02-03 05:32