epam / lib-obj-c-attrSource Code Overview

Analysis scope, overview of main, test, generated, deployment, build, and other code.

Source Code Analysis Scope

Files includes and excluded from analyses

plist

txt

podspec

12 extensions are included in analyses: m, h, plist, gitignore, rb, sh, md, txt, xml, json, podspec, yaml
4 criteria are used to exclude files from analysis:

exclude files with path like ".*/sokrates_.*?[.]json" (Sokrates conventions and configurations) (1 file).
exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (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).

The source code folder contains 166 files:

144 files are included in analyses.
22 files are excluded from analyses:

Explore all 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.

123 files

12 files

4 files

5 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 ".*".

123 files match defined criteria (4,155 LOC, 100.0% vs. main code):

63 *.m files (3,532 LOC)
58 *.h files (384 LOC)
2 *.rb files (239 LOC)

" *.m" is biggest, containing 85.01% of LOC.
" *.rb" is smallest, containing 5.75% of LOC.

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 ".*/TestData/.*".

12 files match defined criteria (191 LOC, 4.6% vs. main code):

6 *.h files (148 LOC)
6 *.m files (43 LOC)

" *.h" is biggest, containing 77.49% of LOC.
" *.m" is smallest, containing 22.51% of LOC.

Build and Deployment Code

Source code used to configure or support build and deployment process.

podspec

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*[.]podspec".
files with paths like ".*[.]git[a-z]+".
files with paths like ".*/[.]gitignore".
files with paths like ".*/build[.]xml".
files with paths like ".*[.]sh".

4 files match defined criteria (54 LOC, 1.3% vs. main code):

1 *.podspec files (20 LOC)
2 *.sh files (17 LOC)
1 *.xml files (17 LOC)

" *.podspec" is biggest, containing 37.04% of LOC.
" *.xml" is smallest, containing 31.48% of LOC.

Other Code

plist

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*[.]plist".
files with paths like ".*[.]json".
files with paths like ".*/[.]gitignore".
files with paths like ".*[.]md".
files with paths like ".*/README[.][a-z0-9]+".
files with paths like ".*[.]txt".

5 files match defined criteria (211 LOC, 5.1% vs. main code):

2 *.md files (121 LOC)
3 *.plist files (90 LOC)

" *.md" is biggest, containing 57.35% of LOC.
" *.plist" is smallest, containing 42.65% of LOC.

Analyzers

Info about analyzers used for source code examinations.

*.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

*.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

*.rb files are analyzed with RubyAnalyzer:

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

Basic heuristic dependency analysis

2025-01-10 14:06