aliyun / alicloud-android-demo - 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

pro

properties

plist

txt

watchmanconfig

cfg

22 extensions are included in analyses: xml, kt, java, gradle, gitignore, js, md, json, pro, properties, plist, bat, m, h, txt, watchmanconfig, xib, bzl, html, mk, cpp, cfg
6 criteria are used to exclude files from analysis:

exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (16 files).
exclude files with path like ".*/proguard[-]rules[.]pro" (ProGuard) (7 files).
exclude files with path like ".*/gradle/wrapper/.*" (Gradle) (3 files).
exclude files with path like ".*/proguard[.]pro" (ProGuard) (1 file).
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 529 files:

361 files are included in analyses.
168 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.

223 files

2 files

27 files

109 files

Main Code

All manually created or maintained source code that defines logic of the product that is run in a production environment.

cfg

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

223 files match defined criteria (8,610 LOC, 100.0% vs. main code):

185 *.xml files (6,692 LOC)
24 *.java files (1,404 LOC)
6 *.js files (361 LOC)
3 *.m files (75 LOC)
1 *.cfg files (34 LOC)
1 *.bzl files (17 LOC)
2 *.h files (15 LOC)
1 *.html files (12 LOC)

" *.xml" is biggest, containing 77.72% of LOC.
" *.html" is smallest, containing 0.14% 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 ".*/test[.].*".
files with paths like ".*__tests__.*".

2 files match defined criteria (50 LOC, 0.6% vs. main code):

1 *.cpp files (44 LOC)
1 *.js files (6 LOC)

" *.cpp" is biggest, containing 88% of LOC.
" *.js" is smallest, containing 12% of LOC.

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 ".*[.]git[a-z]+".
files with paths like ".*/[.]gitignore".
files with paths like ".*[.]gradle".
files with paths like ".*[.]mk".
files with paths like ".*[.]bat".
files with paths like ".*/package[.]json".

27 files match defined criteria (1,164 LOC, 13.5% vs. main code):

13 *.gradle files (533 LOC)
10 *.xml files (412 LOC)
3 *.bat files (200 LOC)
1 *.mk files (19 LOC)

" *.gradle" is biggest, containing 45.79% of LOC.
" *.mk" is smallest, containing 1.63% of LOC.

Other Code

plist

properties

txt

Explore: circles | sunburst

The following criteria are used to filter files:

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

109 files match defined criteria (6,574 LOC, 76.4% vs. main code):

69 *.kt files (4,826 LOC)
17 *.java files (1,068 LOC)
6 *.md files (273 LOC)
4 *.plist files (156 LOC)
8 *.json files (117 LOC)
3 *.properties files (58 LOC)
1 *.xib files (42 LOC)
1 *.txt files (34 LOC)

" *.kt" is biggest, containing 73.41% of LOC.
" *.txt" is smallest, containing 0.52% of LOC.

Analyzers

Info about analyzers used for source code examinations.

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

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

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

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

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

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

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

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

2025-05-15 04:53