alibaba / kubeskoop - 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

proto

mod

ddl

gitattributes

stylelintignore

txt

eslintignore

21 extensions are included in analyses: go, tsx, yaml, css, c, ts, h, svg, md, json, sh, proto, mod, ddl, cjs, gitattributes, stylelintignore, html, gitignore, txt, eslintignore
5 criteria are used to exclude files from analysis:

exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (7 files).
exclude files with path like ".*/docs/.*" (Documentation) (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).
exclude files with path like ".*\.d\.ts" (Typescript definition files) (1 file).

The source code folder contains 426 files:

362 files are included in analyses.
64 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.

308 files

32 files

5 files

17 files

Main Code

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

proto

ddl

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

308 files match defined criteria (34,965 LOC, 100.0% vs. main code):

183 *.go files (25,928 LOC)
37 *.tsx files (3,242 LOC)
18 *.yaml files (1,898 LOC)
11 *.h files (1,455 LOC)
17 *.c files (1,040 LOC)
16 *.ts files (489 LOC)
19 *.css files (356 LOC)
1 *.html files (337 LOC)
4 *.proto files (199 LOC)
2 *.ddl files (21 LOC)

" *.go" is biggest, containing 74.15% of LOC.
" *.ddl" is smallest, containing 0.06% 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 ".*/test[.].*".
files with paths like ".*/[Tt]est/.*".
files with paths like ".*/e2e/.*".

32 files match defined criteria (8,572 LOC, 24.5% vs. main code):

7 *.yaml files (5,321 LOC)
25 *.go files (3,251 LOC)

" *.yaml" is biggest, containing 62.07% of LOC.
" *.go" is smallest, containing 37.93% 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 ".*[.]sh".
files with paths like ".*[.]git[a-z]+".
files with paths like ".*/[.]gitignore".
files with paths like ".*/[.]gitattributes".
files with paths like ".*/package[.]json".

5 files match defined criteria (165 LOC, 0.5% vs. main code). All matches are in *.sh files.

Other Code

mod

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 ".*/[.]gitignore".
files with paths like ".*[.]svg".
files with paths like ".*[.]txt".
files with paths like ".*/[.]stylelintignore".
files with paths like ".*/go[.]mod".
files with paths like ".*/[.]eslintignore".

17 files match defined criteria (6,617 LOC, 18.9% vs. main code):

6 *.json files (5,543 LOC)
3 *.svg files (481 LOC)
6 *.md files (331 LOC)
2 *.mod files (262 LOC)

" *.json" is biggest, containing 83.77% of LOC.
" *.mod" is smallest, containing 3.96% of LOC.

Analyzers

Info about analyzers used for source code examinations.

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

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

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

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

*.c files are analyzed with CStyleAnalyzer:

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

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

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

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

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

*.ddl files are analyzed with SqlAnalyzer:

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

2025-05-14 18:55