instagram / ig-json-parser
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
cfg
txt
properties
  • 12 extensions are included in analyses: java, gradle, kt, xml, md, json, cfg, gitignore, txt, bat, yml, properties
  • 4 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/gradle/wrapper/.*" (Gradle) (1 file).
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (4 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).
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.

main5393 LOC (61%) 72 files
test2054 LOC (23%) 15 files
generated0 LOC (0%) 0 files
build and deployment374 LOC (4%) 18 files
other945 LOC (10%) 23 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 ".*".
  • 72 files match defined criteria (5,393 lines of code, 100.0% vs. main code):
    • 67 *.java files (5,259 lines of code)
    • 5 *.kt files (134 lines of code)
  • " *.java" is biggest, containing 97.52% of code.
  • " *.kt" is smallest, containing 2.48% of code.


*.java5259 LOC (97%) 67 files
*.kt134 LOC (2%) 5 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 ".*/[Tt]est/.*".
  • 15 files match defined criteria (2,054 lines of code, 38.1% vs. main code):
    • 7 *.java files (1,473 lines of code)
    • 8 *.kt files (581 lines of code)
  • " *.java" is biggest, containing 71.71% of code.
  • " *.kt" is smallest, containing 28.29% of code.


*.java1473 LOC (71%) 7 files
*.kt581 LOC (28%) 8 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 ".*/AndroidManifest[.]xml".
    • files with paths like ".*[.]gradle".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]bat".
  • 18 files match defined criteria (374 lines of code, 6.9% vs. main code):
    • 17 *.gradle files (313 lines of code)
    • 1 *.bat files (61 lines of code)
  • " *.gradle" is biggest, containing 83.69% of code.
  • " *.bat" is smallest, containing 16.31% of code.


*.gradle313 LOC (83%) 17 files
*.bat61 LOC (16%) 1 files
Other Code
cfg
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/[Dd]emos?/.*".
    • files with paths like ".*[.]json".
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]properties".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*[.]txt".
  • 23 files match defined criteria (945 lines of code, 17.5% vs. main code):
    • 8 *.java files (472 lines of code)
    • 1 *.md files (151 lines of code)
    • 6 *.xml files (148 lines of code)
    • 1 *.json files (72 lines of code)
    • 2 *.gradle files (52 lines of code)
    • 4 *.kt files (46 lines of code)
    • 1 *.cfg files (4 lines of code)
  • " *.java" is biggest, containing 49.95% of code.
  • " *.cfg" is smallest, containing 0.42% of code.


*.java472 LOC (49%) 8 files
*.md151 LOC (15%) 1 files
*.xml148 LOC (15%) 6 files
*.json72 LOC (7%) 1 files
*.gradle52 LOC (5%) 2 files
*.kt46 LOC (4%) 4 files
*.cfg4 LOC (<1%) 1 files
Analyzers
Info about analyzers used for source code examinations.
  • *.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)
  • *.kt files are analyzed with KotlinAnalyzer:
    • 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 (based on imports and package statements)


2022-04-16 06:55