neo-ai / tvm
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
cmake
txt
mk
pxi
properties
storyboard
plist
pyx
in
clang-format
gitmodules
eslintignore
ini
  • 39 extensions are included in analyses: py, cc, h, sh, rs, rst, md, java, cmake, xml, txt, gitignore, go, toml, c, mk, json, gradle, ts, mm, js, bat, yaml, pxi, yml, properties, storyboard, plist, m, css, pyx, html, in, clang-format, gitmodules, eslintignore, inc, ini, cu
  • 10 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (39 files).
    • exclude files with path like ".*/(3rd|[Tt]hird)[-_]?[Pp]arty/.*" (Dependencies) (9 files).
    • exclude files with path like ".*/target/.*" (Compiled files) (114 files).
    • exclude files with path like ".*/docs/.*" (Documentation) (92 files).
    • exclude files with path like ".*/docs?/_?(build|themes?|templates?|static)/.*" (Sphinx) (0 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 ".*/bin/.*" (Binaries for distribution) (6 files).
    • exclude files with path like ".*[.]txt" (Text files) (31 files).
    • exclude files with path like ".*/sokrates_conventions[.]json" (Sokrates scoping conventions) (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.

main282202 LOC (68%) 1952 files
test120877 LOC (29%) 653 files
generated0 LOC (0%) 0 files
build and deployment2046 LOC (<1%) 100 files
other7151 LOC (1%) 100 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
cmake
pxi
in
pyx
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 1952 files match defined criteria (282,202 lines of code, 100.0% vs. main code):
    • 468 *.cc files (109,997 lines of code)
    • 836 *.py files (105,876 lines of code)
    • 406 *.h files (42,504 lines of code)
    • 71 *.rs files (8,312 lines of code)
    • 18 *.c files (3,497 lines of code)
    • 46 *.cmake files (2,783 lines of code)
    • 40 *.java files (2,765 lines of code)
    • 10 *.ts files (2,170 lines of code)
    • 17 *.go files (1,308 lines of code)
    • 9 *.mm files (1,239 lines of code)
    • 4 *.pxi files (587 lines of code)
    • 12 *.toml files (542 lines of code)
    • 1 *.cu files (359 lines of code)
    • 3 *.yaml files (89 lines of code)
    • 6 *.js files (66 lines of code)
    • 1 *.html files (59 lines of code)
    • 2 *.m files (25 lines of code)
    • 1 *.in files (20 lines of code)
    • 1 *.pyx files (4 lines of code)
  • " *.cc" is biggest, containing 38.98% of code.
  • " *.pyx" is smallest, containing 0% of code.


*.cc109997 LOC (38%) 468 files
*.py105876 LOC (37%) 836 files
*.h42504 LOC (15%) 406 files
*.rs8312 LOC (2%) 71 files
*.c3497 LOC (1%) 18 files
*.cmake2783 LOC (<1%) 46 files
*.java2765 LOC (<1%) 40 files
*.ts2170 LOC (<1%) 10 files
*.go1308 LOC (<1%) 17 files
*.mm1239 LOC (<1%) 9 files
*.pxi587 LOC (<1%) 4 files
*.toml542 LOC (<1%) 12 files
*.cu359 LOC (<1%) 1 files
*.yaml89 LOC (<1%) 3 files
*.js66 LOC (<1%) 6 files
*.html59 LOC (<1%) 1 files
*.m25 LOC (<1%) 2 files
*.in20 LOC (<1%) 1 files
*.pyx4 LOC (<1%) 1 files
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
mk
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/[Tt]ests/.*".
    • files with paths like ".*_test[.].*".
    • files with paths like ".*/test_.*".
    • files with paths like ".*_tests[.].*".
    • files with paths like ".*/[Tt]est/.*".
    • files with any line of content like ".*/simpletest/.*".
  • 653 files match defined criteria (120,877 lines of code, 42.8% vs. main code):
    • 535 *.py files (113,362 lines of code)
    • 36 *.cc files (4,081 lines of code)
    • 7 *.go files (1,056 lines of code)
    • 42 *.sh files (686 lines of code)
    • 12 *.rs files (678 lines of code)
    • 6 *.java files (400 lines of code)
    • 7 *.toml files (198 lines of code)
    • 3 *.js files (147 lines of code)
    • 2 *.mk files (90 lines of code)
    • 1 *.c files (86 lines of code)
    • 1 *.yml files (60 lines of code)
    • 1 *.h files (33 lines of code)
  • " *.py" is biggest, containing 93.78% of code.
  • " *.h" is smallest, containing 0.03% of code.


*.py113362 LOC (93%) 535 files
*.cc4081 LOC (3%) 36 files
*.go1056 LOC (<1%) 7 files
*.sh686 LOC (<1%) 42 files
*.rs678 LOC (<1%) 12 files
*.java400 LOC (<1%) 6 files
*.toml198 LOC (<1%) 7 files
*.js147 LOC (<1%) 3 files
*.mk90 LOC (<1%) 2 files
*.c86 LOC (<1%) 1 files
*.yml60 LOC (<1%) 1 files
*.h33 LOC (<1%) 1 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 ".*[.]mk".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]sh".
    • files with paths like ".*/AndroidManifest[.]xml".
    • files with paths like ".*[.]gradle".
    • files with paths like ".*/[.]gitmodules".
    • files with paths like ".*[.]bat".
    • files with paths like ".*/pom[.]xml".
    • files with paths like ".*/assembly[.]xml".
    • files with paths like ".*/package[.]json".
  • 100 files match defined criteria (2,046 lines of code, 0.7% vs. main code):
    • 76 *.sh files (1,258 lines of code)
    • 10 *.mk files (433 lines of code)
    • 10 *.gradle files (264 lines of code)
    • 4 *.bat files (91 lines of code)
  • " *.sh" is biggest, containing 61.49% of code.
  • " *.bat" is smallest, containing 4.45% of code.


*.sh1258 LOC (61%) 76 files
*.mk433 LOC (21%) 10 files
*.gradle264 LOC (12%) 10 files
*.bat91 LOC (4%) 4 files
Other Code
storyboard
plist
properties
ini
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]properties".
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.]json".
    • files with paths like ".*/[Dd]emos?/.*".
    • files with paths like ".*[.]plist".
    • files with paths like ".*[.]storyboard".
    • files with paths like ".*[.](rst|rest|resttxt|rsttxt)".
    • files with paths like ".*[.]ini".
    • files with paths like ".*/[.]eslintignore".
    • files with paths like ".*/[Ee]xamples/.*".
    • files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
  • 100 files match defined criteria (7,151 lines of code, 2.5% vs. main code):
    • 44 *.md files (4,526 lines of code)
    • 35 *.xml files (1,437 lines of code)
    • 1 *.java files (446 lines of code)
    • 8 *.json files (175 lines of code)
    • 2 *.rs files (139 lines of code)
    • 2 *.storyboard files (139 lines of code)
    • 1 *.py files (107 lines of code)
    • 2 *.plist files (67 lines of code)
    • 3 *.properties files (58 lines of code)
    • 1 *.toml files (31 lines of code)
    • 1 *.ini files (26 lines of code)
  • " *.md" is biggest, containing 63.29% of code.
  • " *.ini" is smallest, containing 0.36% of code.


*.md4526 LOC (63%) 44 files
*.xml1437 LOC (20%) 35 files
*.java446 LOC (6%) 1 files
*.json175 LOC (2%) 8 files
*.rs139 LOC (1%) 2 files
*.storyboard139 LOC (1%) 2 files
*.py107 LOC (1%) 1 files
*.plist67 LOC (<1%) 2 files
*.properties58 LOC (<1%) 3 files
*.toml31 LOC (<1%) 1 files
*.ini26 LOC (<1%) 1 files
Analyzers
Info about analyzers used for source code examinations.
  • *.cc 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
  • *.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
  • *.rs files are analyzed with RustAnalyzer:
    • 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
    • No dependency analysis
  • *.c files are analyzed with CStyleAnalyzer:
    • 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
    • No dependency analysis
  • *.cmake 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
  • *.java files are analyzed with JavaAnalyzer:
    • 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 (based on package names)
  • *.ts files are analyzed with TypeScriptAnalyzer:
    • 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
    • No dependency analysis
  • *.go files are analyzed with GoLangAnalyzer:
    • 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
  • *.mm 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
  • *.pxi 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
  • *.toml 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
  • *.cu 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
  • *.yaml files are analyzed with YamlAnalyzer:
    • 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)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis
  • *.js files are analyzed with JavaScriptAnalyzer:
    • 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
    • No dependency analysis
  • *.html files are analyzed with HtmlAnalyzer:
    • 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
  • *.m 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
  • *.in files are analyzed with RustAnalyzer:
    • 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
    • No dependency analysis
  • *.pyx 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-01 03:12