tensorflow / tfjs
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
npmignore
pb
babelrc
npmrc
txt
plist
properties
proto
project
in
pro
gyp
gitattributes
cfg
prefs
  • 37 extensions are included in analyses: ts, json, js, cc, md, sh, py, h, html, yml, npmignore, pb, bzl, tsx, babelrc, npmrc, txt, css, bat, xml, java, plist, m, gradle, properties, proto, gitignore, project, xib, yaml, in, pro, gyp, gitattributes, svg, cfg, prefs
  • 9 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (68 files).
    • exclude files with path like ".*\.d\.ts" (Typescript definition files) (5 files).
    • exclude files with path like ".*/proguard[-]rules[.]pro" (ProGuard) (1 file).
    • exclude files with path like ".*/gradle/wrapper/.*" (Gradle) (1 file).
    • exclude files with path like ".*/docs/.*" (Documentation) (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) (6 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.

main123762 LOC (44%) 2016 files
test113829 LOC (40%) 595 files
generated16 LOC (<1%) 1 files
build and deployment912 LOC (<1%) 48 files
other42224 LOC (15%) 248 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
proto
gyp
cfg
in
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 2016 files match defined criteria (123,762 lines of code, 100.0% vs. main code):
    • 1,742 *.ts files (93,954 lines of code)
    • 57 *.js files (10,558 lines of code)
    • 101 *.cc files (7,080 lines of code)
    • 24 *.py files (5,986 lines of code)
    • 11 *.tsx files (1,956 lines of code)
    • 15 *.yml files (1,085 lines of code)
    • 39 *.h files (1,063 lines of code)
    • 11 *.bzl files (791 lines of code)
    • 2 *.proto files (740 lines of code)
    • 1 *.css files (183 lines of code)
    • 5 *.html files (125 lines of code)
    • 3 *.m files (96 lines of code)
    • 1 *.gyp files (88 lines of code)
    • 2 *.java files (54 lines of code)
    • 1 *.cfg files (2 lines of code)
    • 1 *.in files (1 lines of code)
  • " *.ts" is biggest, containing 75.92% of code.
  • " *.in" is smallest, containing 0% of code.


*.ts93954 LOC (75%) 1742 files
*.js10558 LOC (8%) 57 files
*.cc7080 LOC (5%) 101 files
*.py5986 LOC (4%) 24 files
*.tsx1956 LOC (1%) 11 files
*.yml1085 LOC (<1%) 15 files
*.h1063 LOC (<1%) 39 files
*.bzl791 LOC (<1%) 11 files
*.proto740 LOC (<1%) 2 files
*.css183 LOC (<1%) 1 files
*.html125 LOC (<1%) 5 files
*.m96 LOC (<1%) 3 files
*.gyp88 LOC (<1%) 1 files
*.java54 LOC (<1%) 2 files
*.cfg2 LOC (<1%) 1 files
*.in1 LOC (<1%) 1 files
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
pb
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*_tests[.].*".
    • files with paths like ".*_test[.].*".
    • files with paths like ".*/test_.*".
    • files with paths like ".*/karma[.]conf[.]js".
    • files with paths like ".*[.][Tt]est[.].*".
    • files with paths like ".*[.]test[.].*".
    • files with paths like ".*/e2e/.*".
    • files with paths like ".*/[Tt]est/.*".
    • files with any line of content like ".*/simpletest/.*".
  • 595 files match defined criteria (113,829 lines of code, 92.0% vs. main code):
    • 469 *.ts files (90,676 lines of code)
    • 53 *.js files (8,502 lines of code)
    • 14 *.pb files (6,752 lines of code)
    • 17 *.py files (4,957 lines of code)
    • 16 *.cc files (1,166 lines of code)
    • 5 *.html files (973 lines of code)
    • 13 *.sh files (304 lines of code)
    • 2 *.bzl files (162 lines of code)
    • 2 *.css files (152 lines of code)
    • 1 *.tsx files (103 lines of code)
    • 2 *.yml files (60 lines of code)
    • 1 *.yaml files (22 lines of code)
  • " *.ts" is biggest, containing 79.66% of code.
  • " *.yaml" is smallest, containing 0.02% of code.


*.ts90676 LOC (79%) 469 files
*.js8502 LOC (7%) 53 files
*.pb6752 LOC (5%) 14 files
*.py4957 LOC (4%) 17 files
*.cc1166 LOC (1%) 16 files
*.html973 LOC (<1%) 5 files
*.sh304 LOC (<1%) 13 files
*.bzl162 LOC (<1%) 2 files
*.css152 LOC (<1%) 2 files
*.tsx103 LOC (<1%) 1 files
*.yml60 LOC (<1%) 2 files
*.yaml22 LOC (<1%) 1 files
Generated Code
Automatically generated files, not manually changed after generation.
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/generated/.*".
  • 1 file matches defined criteria (16 lines of code, 0.0% vs. main code). All matches are in *.java files.


*.java16 LOC (100%) 1 files
Build and Deployment Code
Source code used to configure or support build and deployment process.
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]sh".
    • files with paths like ".*/package[.]json".
    • files with paths like ".*([.]|/)webpack([.]|/).*".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]gradle".
    • files with paths like ".*/AndroidManifest[.]xml".
    • files with paths like ".*[.]bat".
    • files with paths like ".*/[.]gitattributes".
  • 48 files match defined criteria (912 lines of code, 0.7% vs. main code):
    • 38 *.sh files (628 lines of code)
    • 4 *.bat files (123 lines of code)
    • 3 *.gradle files (100 lines of code)
    • 3 *.js files (61 lines of code)
  • " *.sh" is biggest, containing 68.86% of code.
  • " *.js" is smallest, containing 6.69% of code.


*.sh628 LOC (68%) 38 files
*.bat123 LOC (13%) 4 files
*.gradle100 LOC (10%) 3 files
*.js61 LOC (6%) 3 files
Other Code
plist
properties
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]md".
    • files with paths like ".*[.]json".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*/[Dd]emos?/.*".
    • files with paths like ".*/[.]npmignore".
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.]npmrc".
    • files with paths like ".*[.]plist".
    • files with paths like ".*[.]xib".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]properties".
    • files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
  • 248 files match defined criteria (42,224 lines of code, 34.1% vs. main code):
    • 147 *.json files (34,022 lines of code)
    • 54 *.md files (3,383 lines of code)
    • 17 *.js files (2,041 lines of code)
    • 11 *.html files (1,797 lines of code)
    • 6 *.ts files (389 lines of code)
    • 3 *.css files (373 lines of code)
    • 3 *.plist files (113 lines of code)
    • 4 *.xml files (46 lines of code)
    • 1 *.xib files (42 lines of code)
    • 2 *.properties files (18 lines of code)
  • " *.json" is biggest, containing 80.58% of code.
  • " *.properties" is smallest, containing 0.04% of code.


*.json34022 LOC (80%) 147 files
*.md3383 LOC (8%) 54 files
*.js2041 LOC (4%) 17 files
*.html1797 LOC (4%) 11 files
*.ts389 LOC (<1%) 6 files
*.css373 LOC (<1%) 3 files
*.plist113 LOC (<1%) 3 files
*.xml46 LOC (<1%) 4 files
*.xib42 LOC (<1%) 1 files
*.properties18 LOC (<1%) 2 files
Analyzers
Info about analyzers used for source code examinations.
  • *.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
  • *.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
  • *.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
  • *.tsx 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
  • *.yml 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
  • *.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
  • *.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
  • *.proto 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
  • *.css files are analyzed with CssAnalyzer:
    • 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
  • *.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
  • *.gyp 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
  • *.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)
  • *.cfg files are analyzed with CfgAnalyzer:
    • 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
  • *.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

2022-02-03 08:03