aws / jsii
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
snap
txt
csproj
asc
gitattributes
mod
dockerignore
ini
fs
targets
npmrc
in
cmd
fsproj
  • 32 extensions are included in analyses: ts, cs, java, py, md, go, json, gitignore, npmignore, sh, yml, yaml, js, snap, txt, csproj, asc, gitattributes, mod, css, dockerignore, ps1, ini, fs, targets, xml, npmrc, in, svg, toml, cmd, fsproj
  • 7 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (109 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) (9 files).
    • exclude files with path like ".*\.d\.ts" (Typescript definition files) (1 file).
    • exclude files with path like ".*[.]txt" (Text files) (9 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.

main49451 LOC (30%) 513 files
test102645 LOC (64%) 529 files
generated0 LOC (0%) 0 files
build and deployment423 LOC (<1%) 25 files
other7581 LOC (4%) 127 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
asc
targets
in
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 513 files match defined criteria (49,451 lines of code, 100.0% vs. main code):
    • 269 *.ts files (37,597 lines of code)
    • 115 *.cs files (4,794 lines of code)
    • 52 *.go files (2,369 lines of code)
    • 28 *.java files (1,869 lines of code)
    • 16 *.py files (1,301 lines of code)
    • 18 *.js files (586 lines of code)
    • 5 *.asc files (424 lines of code)
    • 2 *.yaml files (200 lines of code)
    • 2 *.ps1 files (112 lines of code)
    • 2 *.css files (109 lines of code)
    • 1 *.yml files (60 lines of code)
    • 1 *.targets files (16 lines of code)
    • 1 *.toml files (11 lines of code)
    • 1 *.in files (3 lines of code)
  • " *.ts" is biggest, containing 76.03% of code.
  • " *.in" is smallest, containing 0.01% of code.


*.ts37597 LOC (76%) 269 files
*.cs4794 LOC (9%) 115 files
*.go2369 LOC (4%) 52 files
*.java1869 LOC (3%) 28 files
*.py1301 LOC (2%) 16 files
*.js586 LOC (1%) 18 files
*.asc424 LOC (<1%) 5 files
*.yaml200 LOC (<1%) 2 files
*.ps1112 LOC (<1%) 2 files
*.css109 LOC (<1%) 2 files
*.yml60 LOC (<1%) 1 files
*.targets16 LOC (<1%) 1 files
*.toml11 LOC (<1%) 1 files
*.in3 LOC (<1%) 1 files
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
snap
csproj
fsproj
fs
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 ".*[.][Tt]est[.].*".
    • files with paths like ".*[.]test[.].*".
    • files with paths like ".*[.]snap".
    • files with paths like ".*/[Tt]ests/.*".
    • files with paths like ".*/test_.*".
    • files with paths like ".*UnitTests/.*".
    • files with any line of content like ".*/simpletest/.*".
  • 529 files match defined criteria (102,645 lines of code, 207.6% vs. main code):
    • 11 *.snap files (78,084 lines of code)
    • 242 *.ts files (13,943 lines of code)
    • 99 *.cs files (5,232 lines of code)
    • 85 *.java files (2,323 lines of code)
    • 9 *.go files (1,789 lines of code)
    • 77 *.py files (1,118 lines of code)
    • 3 *.csproj files (74 lines of code)
    • 1 *.sh files (37 lines of code)
    • 1 *.fsproj files (33 lines of code)
    • 1 *.fs files (12 lines of code)
  • " *.snap" is biggest, containing 76.07% of code.
  • " *.fs" is smallest, containing 0.01% of code.


*.snap78084 LOC (76%) 11 files
*.ts13943 LOC (13%) 242 files
*.cs5232 LOC (5%) 99 files
*.java2323 LOC (2%) 85 files
*.go1789 LOC (1%) 9 files
*.py1118 LOC (1%) 77 files
*.csproj74 LOC (<1%) 3 files
*.sh37 LOC (<1%) 1 files
*.fsproj33 LOC (<1%) 1 files
*.fs12 LOC (<1%) 1 files
Build and Deployment Code
Source code used to configure or support build and deployment process.
csproj
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 ".*/package[.]json".
    • files with paths like ".*/[.]gitattributes".
    • files with paths like ".*[.]csproj".
    • files with paths like ".*([.]|/)webpack([.]|/).*".
  • 25 files match defined criteria (423 lines of code, 0.9% vs. main code):
    • 21 *.sh files (289 lines of code)
    • 3 *.csproj files (83 lines of code)
    • 1 *.js files (51 lines of code)
  • " *.sh" is biggest, containing 68.32% of code.
  • " *.js" is smallest, containing 12.06% of code.


*.sh289 LOC (68%) 21 files
*.csproj83 LOC (19%) 3 files
*.js51 LOC (12%) 1 files
Other Code
mod
ini
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]md".
    • files with paths like ".*[.]txt".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]npmrc".
    • files with paths like ".*[.]json".
    • files with paths like ".*/go[.]mod".
    • files with paths like ".*/[.]npmignore".
    • files with paths like ".*[.]ini".
    • files with paths like ".*/[Ee]xamples/.*".
    • files with paths like ".*/[.]dockerignore".
    • files with paths like ".*[.]svg".
    • files with paths like ".*[.](xml|xsd|robot|sql|pgsql|dashboard|profile|ipynb|raml|avsc|al)".
  • 127 files match defined criteria (7,581 lines of code, 15.3% vs. main code):
    • 64 *.md files (5,712 lines of code)
    • 51 *.json files (1,696 lines of code)
    • 4 *.ts files (62 lines of code)
    • 3 *.mod files (46 lines of code)
    • 1 *.svg files (32 lines of code)
    • 2 *.xml files (29 lines of code)
    • 2 *.ini files (4 lines of code)
  • " *.md" is biggest, containing 75.35% of code.
  • " *.ini" is smallest, containing 0.05% of code.


*.md5712 LOC (75%) 64 files
*.json1696 LOC (22%) 51 files
*.ts62 LOC (<1%) 4 files
*.mod46 LOC (<1%) 3 files
*.svg32 LOC (<1%) 1 files
*.xml29 LOC (<1%) 2 files
*.ini4 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
  • *.cs files are analyzed with CSharpAnalyzer:
    • 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 namespace heuristics)
  • *.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
  • *.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)
  • *.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
  • *.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
  • *.asc 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
  • *.ps1 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
  • *.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
  • *.targets files are analyzed with XmlAnalyzer:
    • 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
  • *.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
  • *.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-01-31 14:47