tensorflow / haskell
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
hs
txt
cabal
chs
pb
gitmodules
nix
  • 15 extensions are included in analyses: html, hs, css, js, json, txt, cabal, sh, md, gitignore, chs, pb, gitmodules, nix, yaml
  • 6 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (2 files).
    • exclude files with path like ".*/docs/.*" (Documentation) (153 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) (0 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.

main7142 LOC (73%) 53 files
test2166 LOC (22%) 21 files
generated0 LOC (0%) 0 files
build and deployment48 LOC (<1%) 3 files
other318 LOC (3%) 7 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
hs
cabal
pb
chs
nix
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 53 files match defined criteria (7,142 lines of code, 100.0% vs. main code):
    • 38 *.hs files (5,702 lines of code)
    • 11 *.cabal files (924 lines of code)
    • 1 *.pb files (361 lines of code)
    • 1 *.chs files (115 lines of code)
    • 1 *.yaml files (23 lines of code)
    • 1 *.nix files (17 lines of code)
  • " *.hs" is biggest, containing 79.84% of code.
  • " *.nix" is smallest, containing 0.24% of code.


*.hs5702 LOC (79%) 38 files
*.cabal924 LOC (12%) 11 files
*.pb361 LOC (5%) 1 files
*.chs115 LOC (1%) 1 files
*.yaml23 LOC (<1%) 1 files
*.nix17 LOC (<1%) 1 files
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
hs
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 ".*[.][Tt]est[.].*".
    • files with paths like ".*_tests[.].*".
    • files with any line of content like ".*/simpletest/.*".
  • 21 files match defined criteria (2,166 lines of code, 30.3% vs. main code):
    • 20 *.hs files (2,160 lines of code)
    • 1 *.sh files (6 lines of code)
  • " *.hs" is biggest, containing 99.72% of code.
  • " *.sh" is smallest, containing 0.28% of code.


*.hs2160 LOC (99%) 20 files
*.sh6 LOC (<1%) 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 ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/[.]gitmodules".
  • 3 files match defined criteria (48 lines of code, 0.7% vs. main code). All matches are in *.sh files.


*.sh48 LOC (100%) 3 files
Other Code
hs
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 ".*/[Ee]xamples/.*".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]txt".
  • 7 files match defined criteria (318 lines of code, 4.5% vs. main code):
    • 3 *.md files (174 lines of code)
    • 3 *.hs files (138 lines of code)
    • 1 *.json files (6 lines of code)
  • " *.md" is biggest, containing 54.72% of code.
  • " *.json" is smallest, containing 1.89% of code.


*.md174 LOC (54%) 3 files
*.hs138 LOC (43%) 3 files
*.json6 LOC (1%) 1 files
Analyzers
Info about analyzers used for source code examinations.
  • *.hs 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
  • *.cabal 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
  • *.pb 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
  • *.chs 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
  • *.nix 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-02-03 07:59